On Wed, Sep 17, 2014 at 07:42:54AM +1000, Dave Chinner wrote: > [Please don't top post!] > > On Tue, Sep 16, 2014 at 03:45:52PM -0400, Milosz Tanski wrote: > > On Tue, Sep 16, 2014 at 3:27 PM, Jeff Moyer <jmoyer@xxxxxxxxxx> wrote: > > > Christoph Hellwig <milosz@xxxxxxxxx> writes: > > > > > > Hrm, you're not Christoph... > > > > I am not Christoph, we collaborated and he sent me this patch. > > You're missing Jeff's point - have a look at the name and email > adress the mail appears to be from. It's completely mangled - forged > if you will and Linus had a major rant about doing exactly this to > patch sereies recently. There is a perfectly acceptible way of > crediting who the patch is from correctly without resorting to games > like this. Linus flamed me for that a few weeks ago. The problem is that if one uses "git format-patch" to prepare a series of emails to post, that it users the patch's author for the From: entry. I think that is a bug in git since multiple people have encountered this issue. It's not like git doesn't know what one's email address is.... -ben > Also, this patch doesn't have a description or a valid SOB on it.... > > Please read Documentation/SubmittingPatches so you get the format of > the patches correct for V2. ;) > > Cheers, > > Dave. > -- > Dave Chinner > david@xxxxxxxxxxxxx > > -- > To unsubscribe, send a message with 'unsubscribe linux-aio' in > the body to majordomo@xxxxxxxxx. For more info on Linux AIO, > see: http://www.kvack.org/aio/ > Don't email: <a href=mailto:"aart@xxxxxxxxx";>aart@xxxxxxxxx</a> -- "Thought is the essence of where you are now." -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
