From: Baruch Siach <baruch@tkos.co.il>
To: Joe Perches <joe@perches.com>
Cc: git@vger.kernel.org, Rasmus Villemoes <rv@rasmusvillemoes.dk>
Subject: Re: [PATCH] send-email: don't cc *-by lines with '-' prefix
Date: Sat, 16 Mar 2019 22:14:10 +0200 [thread overview]
Message-ID: <87y35eziel.fsf@tarshish> (raw)
In-Reply-To: <fc14d671d5c3ff43fc43095930d4c762fe6f5002.camel@perches.com>
Hi Joe,
On Sat, Mar 16 2019, Joe Perches wrote:
> On Sat, 2019-03-16 at 21:49 +0200, Baruch Siach wrote:
>> On Sat, Mar 16 2019, Joe Perches wrote:
>> > On Sat, 2019-03-16 at 21:26 +0200, Baruch Siach wrote:
>> > > Since commit ef0cc1df90f6b ("send-email: also pick up cc addresses from
>> > > -by trailers") in git version 2.20, git send-email adds to cc list
>> > > addresses from all *-by lines. As a side effect a line with
>> > > '-Signed-off-by' is now also added to cc. This makes send-email pick
>> > > lines from patches that remove patch files from the git repo. This is
>> > > common in the Buildroot project that often removes (and adds) patch
>> > > files that have 'Signed-off-by' in their patch description part.
>> >
>> > Why is such a line used and why shouldn't an author
>> > of a to-be-removed patch be cc'd?
>>
>> These lines are currently used because the '^([a-z-]*-by)' regexp
>> matches.
>
> That part I already understood.
>
> I am not a buildroot user.
>
>> Buildroot is a tool that build various software packages. The patches
>> being removed are usually for packages that Buildroot patches to fix the
>> build. These patches are often pulled from upstream git repo of
>> respective package. When the package version updates, the patch is
>> dropped.
>>
>> We don't cc patch authors when we add the patch in the first place,
>> because the regexp does not match '+Signed-off-by'. I see not reason to
>> cc them when we remove the patch.
>
> So buildroot uses '+Signed-off-by:' and '-Signed-off-by:' lines
> for some internal purpose?
>
> Why?
>
> https://buildroot.org/downloads/manual/manual.html
>
> doesn't mention it.
No. Patches to the Buildroot project often add or remove patch
files. See this one for example:
http://lists.busybox.net/pipermail/buildroot/2019-March/244762.html
In this case 'git send-email' added Peter Korsgaard to cc because a
patch file with his sign-off is removed.
(mbox) Adding cc: Baruch Siach <baruch@tkos.co.il> from line 'From: Baruch Siach <baruch@tkos.co.il>'
(body) Adding cc: Petr Vorel <petr.vorel@gmail.com> from line 'Cc: Petr Vorel <petr.vorel@gmail.com>'
(body) Adding cc: Baruch Siach <baruch@tkos.co.il> from line 'Signed-off-by: Baruch Siach <baruch@tkos.co.il>'
(body) Adding cc: Peter Korsgaard <peter@korsgaard.com> from line '-Signed-off-by: Peter Korsgaard <peter@korsgaard.com>'
The same Buildroot patch also adds a patch file that carries a number of
sign-off lines. But 'git send-email didn't add these addresses to cc.
In both cases I see not point in adding these addresses to cc, since
they have little to do with the Buildroot patch. But only patch removal
triggers the regexp.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2019-03-16 20:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 19:26 [PATCH] send-email: don't cc *-by lines with '-' prefix Baruch Siach
2019-03-16 19:30 ` Joe Perches
2019-03-16 19:49 ` Baruch Siach
2019-03-16 19:59 ` Joe Perches
2019-03-16 20:14 ` Baruch Siach [this message]
2019-03-16 20:23 ` Joe Perches
2019-03-17 19:27 ` Rasmus Villemoes
2019-03-18 1:56 ` Joe Perches
2019-03-18 6:28 ` Junio C Hamano
2019-03-18 7:02 ` Joe Perches
2019-04-04 7:38 ` Baruch Siach
2019-04-04 9:20 ` Junio C Hamano
2019-04-04 9:27 ` Baruch Siach
2019-04-04 9:41 ` Junio C Hamano
2019-04-04 9:42 ` Rasmus Villemoes
2019-04-04 9:47 ` Junio C Hamano
2019-04-04 12:14 ` Jeff King
2019-04-04 9:49 ` 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=87y35eziel.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=git@vger.kernel.org \
--cc=joe@perches.com \
--cc=rv@rasmusvillemoes.dk \
/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.