From: Jeff Garzik <jeff@garzik.org>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Hans-Peter Jansen <hpj@urpla.net>,
linux-kernel@vger.kernel.org, James.Bottomley@steeleye.com,
nick.cheng@areca.com.tw
Subject: Re: arcmsr changelog differs from diffs
Date: Wed, 17 Oct 2007 18:34:37 -0400 [thread overview]
Message-ID: <47168DFD.6030900@garzik.org> (raw)
In-Reply-To: <20071017130145.GA15918@atjola.homenet>
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
prev parent reply other threads:[~2007-10-17 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 22:07 arcmsr changelog differs from diffs Hans-Peter Jansen
2007-10-17 0:53 ` Björn Steinbrink
2007-10-17 10:41 ` Hans-Peter Jansen
2007-10-17 13:01 ` Björn Steinbrink
2007-10-17 22:34 ` Jeff Garzik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47168DFD.6030900@garzik.org \
--to=jeff@garzik.org \
--cc=B.Steinbrink@gmx.de \
--cc=James.Bottomley@steeleye.com \
--cc=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.cheng@areca.com.tw \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox