lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1472672344.4176.32.camel@perches.com>
Date:   Wed, 31 Aug 2016 12:39:04 -0700
From:   Joe Perches <joe@...ches.com>
To:     Junio C Hamano <gitster@...ox.com>
Cc:     git@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] git-send-email: Add ability to cc: any "bylines" in
 the commit message

On Wed, 2016-08-31 at 12:34 -0700, Junio C Hamano wrote:
> Joe Perches <joe@...ches.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?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ