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] [day] [month] [year] [list]
Date:	Wed, 17 Oct 2007 18:34:37 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Björn Steinbrink <B.Steinbrink@....de>
CC:	Hans-Peter Jansen <hpj@...la.net>, linux-kernel@...r.kernel.org,
	James.Bottomley@...eleye.com, nick.cheng@...ca.com.tw
Subject: Re: arcmsr changelog differs from diffs

Björn Steinbrink wrote:
> Hi Hans,
> 
> On 2007.10.17 12:41:11 +0200, Hans-Peter Jansen wrote:
>> Dear Björn,
>>
>> Am Mittwoch, 17. Oktober 2007 02:53 schrieb Björn Steinbrink:
>>> And then, if I may guess, James probably just noticed that there were
>>> changes left and commited them (while they were now down to just the
>>> whitespace change), without checking what changes were actually left (no
>>> offense intended). At least I think that git wouldn't cripple the diff
>>> if the changes that James checked in were not already whitespace-only at
>>> the time he commited them, and the git history of his tree seems to
>>> agree.
>> (*) Thanks for the clarification, Björn. What made me stumbling was the 
>> different orginators, while Jeff isn't known with catching attention by 
>> assimilating other peoples contributions. 
> 
> I'm just guessing here, and certainly don't want to blame anyone, but
> Jeff's original patch was from July, while the only date I can find for
> Nick's commit is September 13th. So it was probably Nick who integrated
> Jeff's changes into his commit 

Correct.

It's also quite normal for the maintainer to grab a patch off the list, 
integrate/massage/change it, and then apply it himself.

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ