From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Mingming Cao <cmm@us.ibm.com>, Theodore Tso <tytso@mit.edu>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: finding the author of the patches in ext4-patch-queue
Date: Wed, 04 Jul 2007 10:37:01 +0530 [thread overview]
Message-ID: <468B2AF5.5060207@linux.vnet.ibm.com> (raw)
Hi Mingming,
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.
with the below diff to noextent_mount option patch i get the below history when applying the patches
using stgit via stgit --import --series
diff --git a/ext4_noextent_mount_opt.patch b/ext4_noextent_mount_opt.patch
index c349afb..e9a8d6f 100644
--- a/ext4_noextent_mount_opt.patch
+++ b/ext4_noextent_mount_opt.patch
@@ -1,3 +1,4 @@
+From: Mingming Cao <cmm@us.ibm.com>
Add a mount option to turn off extents.
Signed-off-by: Mingming Cao <cmm@us.ibm.com>
$ git log
commit f89bcb4ca03dde8b12d3c722483aae84c3d2072d
Author: Mingming Cao <cmm@us.ibm.com>
Date: Wed Jul 4 10:32:19 2007 +0530
Add a mount option to turn off extents.
Signed-off-by: Mingming Cao <cmm@us.ibm.com>
Without the change: I get below
commit 4a4f228f99e263767fe5b395cdb843a5c5d083fe
Author: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Date: Wed Jul 4 10:05:19 2007 +0530
Turn on extents feature by default in ext4 filesystem. User could use
-o noextents to turn it off.
Signed-off-by: Mingming Cao <cmm@us.ibm.com>
-aneesh
next reply other threads:[~2007-07-04 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 5:07 Aneesh Kumar K.V [this message]
2007-07-04 3:27 ` finding the author of the patches in ext4-patch-queue Mingming Cao
2007-07-05 4:54 ` Andreas Dilger
2007-07-05 13:40 ` Dave Kleikamp
2007-07-05 14:26 ` Theodore Tso
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=468B2AF5.5060207@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
/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).