From: Theodore Ts'o <tytso@mit.edu>
To: gregoire.pichon@bull.net
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs patch proposal
Date: Sat, 15 Dec 2012 22:39:39 -0500 [thread overview]
Message-ID: <20121216033939.GA5663@thunk.org> (raw)
In-Reply-To: <OF02F0D2AC.047670E1-ONC1257AD2.004E43DF-C1257AD2.004E9441@bull.net>
Applied. In general, it's more convenient to use "git format-patch"
and "git send-email" to submit patches, but it's not a big deal. Use
of those two commands just saves me a little bit of manual work
dealing with the patch.
Thanks for the patch and the bug report!
- Ted
parent reply other threads:[~2012-12-16 3:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <OF02F0D2AC.047670E1-ONC1257AD2.004E43DF-C1257AD2.004E9441@bull.net>]
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=20121216033939.GA5663@thunk.org \
--to=tytso@mit.edu \
--cc=gregoire.pichon@bull.net \
--cc=linux-ext4@vger.kernel.org \
/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).