From: Theodore Tso <tytso@mit.edu>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Mingming Cao <cmm@us.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: finding the author of the patches in ext4-patch-queue
Date: Thu, 5 Jul 2007 10:26:02 -0400 [thread overview]
Message-ID: <20070705142602.GE341@thunk.org> (raw)
In-Reply-To: <20070705045416.GA5633@schatzie.adilger.int>
On Wed, Jul 04, 2007 at 10:54:16PM -0600, Andreas Dilger wrote:
> On Jul 03, 2007 23:27 -0400, Mingming Cao wrote:
> > On Wed, 2007-07-04 at 10:37 +0530, Aneesh Kumar K.V wrote:
> > > With respect to ext4-patch-queue it is kind of difficult to find who wrote the patch.
> > > I guess we can solve this by adding From: < author name > in the patches. This will make sure
> > > when the patches get applied to linus tree we have the right author.
> > >
> >
> > Thanks, Aneesh, I will add From: <authro> for all patches in ext4 patch
> > queue.
>
> You may as well add "Signed-off-by: <author>", since that is the standard
> way to do this. If you have any questions about who wrote a particular
> CFS patch I can tell you.
In general the first Signed-off-by: is the author, yes. I believe
what Aneesh is talking about is formatting the patches so that when
they are pulled into git, "git log" shows the correct author information.
- Ted
prev parent reply other threads:[~2007-07-05 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 5:07 finding the author of the patches in ext4-patch-queue Aneesh Kumar K.V
2007-07-04 3:27 ` Mingming Cao
2007-07-05 4:54 ` Andreas Dilger
2007-07-05 13:40 ` Dave Kleikamp
2007-07-05 14:26 ` Theodore Tso [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=20070705142602.GE341@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).