public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes
Date: Wed, 08 Apr 2009 15:08:14 -0400	[thread overview]
Message-ID: <49DCF61E.2000703@garzik.org> (raw)
In-Reply-To: <20090408185639.GL20983@parisc-linux.org>

Matthew Wilcox wrote:
> On Wed, Apr 08, 2009 at 02:47:43PM -0400, Jeff Garzik wrote:
>> Matthew Wilcox wrote:
>>> On Wed, Apr 08, 2009 at 02:59:55AM -0400, Jeff Garzik wrote:
>>>> I checked this into libata-dev.git#sectsize and #NEXT...  comments
>>>> welcome.  It's willy's patch, cut down such that it introduces no
>>>> major behavior changes [READ CAPACITY improves slightly].
>>> Umm.  If you wanted me to split the patch up, why didn't you ask?
>> I've had trouble until recently simply getting you to post patches at 
>> all.  It was faster and simpler for me to do it myself.
> 
> ?!  Are you referring to the one incident where you asked me if I had
> any patches for 2.6.30, I pointed at the TRIM patches and you quibbled
> that I hadn't reposted the updates, only a git tree?

On multiple occasions.  You're the only one I have to poke to get 
updates on pending libata patches, in some cases, patches that really 
should have gone upstream long ago.


>>> I really do think I should be credited as 'Author' here.  You credit me
>>> in the patch description, but the automated tools don't show that.
>> If that is your preference, that's fine.  I did it this way to avoid 
>> your taking the blame for anything I did, while still noting in the 
>> patch description you did the original work.
> 
> Yes, that's my preference.  It's also the documented way to do things in
> SubmittingPatches.

The patch was changed from your original work, in several places.  That 
makes the issue of From header not so clear cut.  See what I said about 
blame etc. in the original email :)  If there were bugs in my changes, 
you would probably be annoyed to get bug reports about that :)

	Jeff



  reply	other threads:[~2009-04-08 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  6:59 [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes Jeff Garzik
2009-04-08 18:32 ` Matthew Wilcox
2009-04-08 18:47   ` Jeff Garzik
2009-04-08 18:56     ` Matthew Wilcox
2009-04-08 19:08       ` Jeff Garzik [this message]
2009-04-08 19:13         ` Matthew Wilcox

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=49DCF61E.2000703@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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