From: Theodore Ts'o <tytso@mit.edu>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] fully and properly gettextize two error messages in e2fsck
Date: Sun, 1 Jun 2014 21:19:26 -0400 [thread overview]
Message-ID: <20140602011926.GB6248@thunk.org> (raw)
In-Reply-To: <1401658069.328.123945581.4DB549FE@webmail.messagingengine.com>
Thanks, applied.
BTW, it's much better to use git send-email to send a patch series.
That way, the patches are properly chained which makes it easier for
me to find and apply the messages in the proper order. Also, that way
I can review the patch, and if it's Obviously Correct (tm), I can just
add it to a unix mbox file, and then apply a set of patches using the
"git am" command.
Cheers,
- Ted
next prev parent reply other threads:[~2014-06-02 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 21:27 [PATCH] fully and properly gettextize two error messages in e2fsck Benno Schulenberg
2014-06-02 1:19 ` Theodore Ts'o [this message]
2014-06-02 19:47 ` Benno Schulenberg
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=20140602011926.GB6248@thunk.org \
--to=tytso@mit.edu \
--cc=bensberg@justemail.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).