From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH -v3] ext4: refactor duplicated block placement code
Date: Tue, 28 Jun 2011 10:44:49 -0400 [thread overview]
Message-ID: <20110628144449.GK2729@thunk.org> (raw)
In-Reply-To: <4E09E1C8.9020107@redhat.com>
On Tue, Jun 28, 2011 at 09:14:32AM -0500, Eric Sandeen wrote:
> On 6/28/11 9:05 AM, Theodore Ts'o wrote:
> > From: "Theodore Ts'o" <tytso@mit.edu>
>
> I kind of wish you'd keep me on the From: even if you did
> move the change to a new file.
No worries, you are still the author in the git commit.
The From that you saw was becasue because I edited the output of
git-format-patch before I used git send-email, forgetting that git
send-email would fix up the from field and move the original From
field into the budy of the message.
- Ted
next prev parent reply other threads:[~2011-06-28 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 18:37 [PATCH] ext4: refactor duplicated block placement code Eric Sandeen
2011-06-23 3:16 ` Andreas Dilger
2011-06-23 14:56 ` Eric Sandeen
2011-06-27 20:39 ` [PATCH V2] " Eric Sandeen
2011-06-28 14:05 ` [PATCH -v3] " Theodore Ts'o
2011-06-28 14:14 ` Eric Sandeen
2011-06-28 14:44 ` Ted Ts'o [this message]
2011-06-28 14:45 ` Eric Sandeen
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=20110628144449.GK2729@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).