Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Aleksandr Lyapunov <alyapunov@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] tools: add a script that checks submodules' commits
Date: Wed, 24 Mar 2021 03:25:40 +0300	[thread overview]
Message-ID: <20210324002540.5kerayajlanmrwk4@tkn_work_nb> (raw)
In-Reply-To: <1616066671-24689-1-git-send-email-alyapunov@tarantool.org>

Nice idea :)

I don't mind any scripts that ease developer / maintainer life.

The patch is okay for push (from my point of view), however I would
share some thoughts around. Feel free to pass them over if you don't
want to pay more time here.

I would extend the script for all long-term branches (1.10, 2.*, master)
with a submodule specific rules:

1. test-run's commit should be reachable from test-run's master for all
   long-term branches.
2. I guess it is the same for small, but from what I heard, we possibly
   will fork a stable branch. So the rule will be like (not sure about X
   value):
   - if tarantool's branch is 1.10 / 2.X (X < 8) => small's commit should
     be reachable from small's tarantool-1.10 branch.
   - 2.X (X >= 8), master => reachable from small's master.
3. There is master and tarantool-1.10 in msgpuck, similar to above.

I would also explicitly skip the checks for pushing to any other branch.
So the script may be called before any push and may be integrated into
`.git/hooks/pre-push`. This means, a maintainer will place it here once
and will not need to run it manually.

Maybe it worth to look at the `.git/hooks/pre-push` format from
beginning. At least it accepts a branch to push as the second parameter
that may be useful.

Anyway, the script is useful without those enhancements.

WBR, Alexander Turenko.

> When the fix is merged to mater it's very simple to make a mistake:

Just if'll spin around again: mater -> master.

      reply	other threads:[~2021-03-24  0:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 11:24 Aleksandr Lyapunov via Tarantool-patches
2021-03-24  0:25 ` Alexander Turenko via Tarantool-patches [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210324002540.5kerayajlanmrwk4@tkn_work_nb \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=alyapunov@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] tools: add a script that checks submodules'\'' commits' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox