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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 29 Nov 2017 22:37:54 +1100
From:   NeilBrown <neilb@...e.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Oleg Drokin <oleg.drokin@...el.com>,
        Andreas Dilger <andreas.dilger@...el.com>,
        James Simmons <jsimmons@...radead.org>,
        linux-kernel@...r.kernel.org, lustre-devel@...ts.lustre.org
Subject: Re: [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c

On Wed, Nov 29 2017, Greg Kroah-Hartman wrote:

> On Wed, Nov 29, 2017 at 02:01:12PM +1100, NeilBrown wrote:
>> Subject: [PATCH] staging: lustre: lov: use list_for_each_entry in lov_obd.c
>
> Why is there a subject line in the body of the text here?  Will git
> figure this out correctly?

Because I wanted to leave the original subject unchanged so it would be
fairly clear to you the context of the email, but also wanted to be
certain picked up the right subject (though in this case it would have
worked right anyway I think).
Yes, "git am" will see the Subject: line in the body and over-ride the
Subject line in the headers.

Thanks,
NeilBrown


>
>> Using the *_entry macro simplifies the code slightly.
>> 
>> Signed-off-by: NeilBrown <neilb@...e.com>
>> ---
>> 
>> Resubmitted with non-empty changelog text.
>
> Did I apply the others?  Can you just send a new series of whatever I
> didn't apply so it's obvious for me as to what to do?
>
> thanks,
>
> greg k-h

Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)

Powered by blists - more mailing lists