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

Re: [PATCH V2] git-send-email: Add ability to cc: any "bylines" in the commit message

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 31, 2016, 20:09 UTC
Message-ID
<xmqqr394zon1.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1472672344.4176.32.camel@perches.com>
Joe Perches <joe@perches.com> writes:
Show 24 quoted lines
> On Wed, 2016-08-31 at 12:34 -0700, Junio C Hamano wrote:
>> Joe Perches <joe@perches.com> writes:
>> > Many commits have various forms of bylines similar to
>> A missing blank line (I can tweak while queuing).
> []
>> > +				next if $suppress_cc{'bylines'} and $what !~ /Signed-off-by/i and $what =~ /by$/i;
>> Having to keep this /by$/i in sync with whatever definition of
>> bylines is will be error prone.  How about doing it in this way?
>> 
>> 	# Now parse the message body
>> +	my $bypat = r/[\w-]+-by/;
>> 	while (<$fh>) {
>>         	...
>>                 if (/^(Signed-off-by|Cc|$bypat): (.*)$/i) {
>>                 	...
>>                         	next if $suppress_cc{'bodycc'} and $what =~ /Cc/i;
>> +				next if $suppress_cc{'bylines'} and
>> +					$what !~ /^Signed-off-by/i and
>> +					$what =~ /^$bypat/i;
>> 
>> Other than that, looking good.
>
> Sure, whatever you want, do you want a v3 from me or can
> you fix it up however you want?

This topic is not my itch, so "however I want" would not be a good instruction to me--The lazy one in me would be tempted to say "ok, then I'd drop it altogether" ;-)

I am sure the typo "[^\s]+[\w-]by" in the one we just saw was merely because you rushed it out without double checking. We are in pre-release feature freeze so there is no need to rush. I'd prefer to see a final version that is carefully proof-read by the author.

Thanks.
Previous: Joe PerchesNext: Jeff Kirsher
Message 4 of 5 in “git-send-email: Add ability to cc: any "bylines" in the commit message”
  1. git-send-email: Add ability to cc: any "bylines" in the commit messageJoe Perches, Aug 31, 2016
  2. Junio C HamanoAug 31, 2016
  3. Joe PerchesAug 31, 2016
  4. Junio C HamanoAug 31, 2016
  5. Jeff KirsherAug 31, 2016

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.