git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] send-email: don't cc *-by lines with '-' prefix

From
Baruch Siach <baruch@tkos.co.il>
Date
Mar 16, 2019, 20:14 UTC
Message-ID
<87y35eziel.fsf@tarshish>
In-Reply-To
<fc14d671d5c3ff43fc43095930d4c762fe6f5002.camel@perches.com>
Hi Joe,
On Sat, Mar 16 2019, Joe Perches wrote:
Show 39 quoted lines
> 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 -
Previous: Joe PerchesNext: Joe Perches
Message 5 of 18 in “send-email: don't cc *-by lines with '-' prefix”
  1. send-email: don't cc *-by lines with '-' prefixBaruch Siach, Mar 16, 2019
  2. Joe PerchesMar 16, 2019
  3. Baruch SiachMar 16, 2019
  4. Joe PerchesMar 16, 2019
  5. Baruch SiachMar 16, 2019
  6. Joe PerchesMar 16, 2019
  7. Rasmus VillemoesMar 17, 2019
  8. Joe PerchesMar 18, 2019
  9. Junio C HamanoMar 18, 2019
  10. Joe PerchesMar 18, 2019
  11. Baruch SiachApr 4, 2019
  12. Junio C HamanoApr 4, 2019
  13. Baruch SiachApr 4, 2019
  14. Junio C HamanoApr 4, 2019
  15. Rasmus VillemoesApr 4, 2019
  16. Junio C HamanoApr 4, 2019
  17. Junio C HamanoApr 4, 2019
  18. Jeff KingApr 4, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.