From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: git@vger.kernel.org, msuchanek@suse.de, Till Maas <tmaas@redhat.com>
Subject: Re: [PATCH v2] tests: do not use "slave branch" nomenclature
Date: Fri, 19 Jun 2020 20:00:58 +0700 [thread overview]
Message-ID: <20200619130058.GA5027@danh.dev> (raw)
In-Reply-To: <20200619093210.31289-1-pbonzini@redhat.com>
On 2020-06-19 11:32:10+0200, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Git branches have been qualified as topic branches, integration branches,
> development branches, feature branches, release branches and so on.
> Git has a branch that is the master *for* development, but it is not
> the master *of* any "slave branch": Git does not have slave branches,
> and has never had, except for a single testcase that claims otherwise. :)
reading this text and the change may give the impression that this is
used for feature branch only.
I think common terminology in Git's test is this kind of branch is side.
In this inaccurate comparison:
git grep -E '(branch|checkout|switch).* side '
git grep -E '(branch|checkout|switch).* feature'
The former yields more result than the latter.
The latter shows only t1090 and t3420.
If I were writing this patch, I would go with the former.
<xmqqr1umg8fp.fsf@gitster.c.googlers.com> seems to prefer side, too.
Other than that, the patch looks good to me.
>
> Independent of any future change to the naming of the "master" branch,
> removing this sole appearance of the term is a strict improvement: it
> avoids divisive language, and talking about "feature branch" clarifies
> which developer workflow the test is trying to emulate.
>
> Reported-by: Till Maas <tmaas@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> t/t4014-format-patch.sh | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/t/t4014-format-patch.sh b/t/t4014-format-patch.sh
> index 575e079cc2..958c2da56e 100755
> --- a/t/t4014-format-patch.sh
> +++ b/t/t4014-format-patch.sh
> @@ -81,16 +81,16 @@ test_expect_success 'format-patch --ignore-if-in-upstream handles tags' '
> '
>
> test_expect_success "format-patch doesn't consider merge commits" '
> - git checkout -b slave master &&
> + git checkout -b feature master &&
> echo "Another line" >>file &&
> test_tick &&
> - git commit -am "Slave change #1" &&
> + git commit -am "Feature branch change #1" &&
> echo "Yet another line" >>file &&
> test_tick &&
> - git commit -am "Slave change #2" &&
> + git commit -am "Feature branch change #2" &&
> git checkout -b merger master &&
> test_tick &&
> - git merge --no-ff slave &&
> + git merge --no-ff feature &&
> git format-patch -3 --stdout >patch &&
> grep "^From " patch >from &&
> test_line_count = 3 from
> --
> 2.25.4
>
--
Danh
next prev parent reply other threads:[~2020-06-19 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 9:32 [PATCH v2] tests: do not use "slave branch" nomenclature Paolo Bonzini
2020-06-19 13:00 ` Đoàn Trần Công Danh [this message]
2020-06-19 14:23 ` Paolo Bonzini
2020-06-19 13:27 ` Kaartic Sivaraam
2020-06-19 17:18 ` Junio C Hamano
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=20200619130058.GA5027@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=pbonzini@redhat.com \
--cc=tmaas@redhat.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.