From: Theodore Tso <tytso@mit.edu>
To: Michael Roth <mroth@nessie.de>
Cc: linux-fsdevel@vger.kernel.org, tytso@alum.mit.edu
Subject: Re: [PATCH 0/2) e2fsprogs: Two small patches
Date: Sat, 24 Oct 2009 14:29:38 -0400 [thread overview]
Message-ID: <20091024182938.GB18523@mit.edu> (raw)
In-Reply-To: <1255778811-12280-1-git-send-email-mroth@nessie.de>
On Sat, Oct 17, 2009 at 01:26:49PM +0200, Michael Roth wrote:
> Two small patches for e2fsprogs:
>
> .gitignore | 23 +++++++++++++++++++++++
> misc/Makefile.in | 5 +++--
> 2 files changed, 26 insertions(+), 2 deletions(-)
Thanks, I've accepted the update to .gitignore. As far as e4defrag,
I'm not yet 100% convinced I'm confident enough in it to want to be
installing it by default just yet.
- Ted
prev parent reply other threads:[~2009-10-24 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 11:26 [PATCH 0/2) e2fsprogs: Two small patches Michael Roth
2009-10-17 11:26 ` [PATCH 1/2] e4defrag: install binary and man page Michael Roth
2009-10-17 18:41 ` Eric Sandeen
2009-10-17 11:26 ` [PATCH 2/2] Update .gitignore Michael Roth
2009-10-24 18:29 ` 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=20091024182938.GB18523@mit.edu \
--to=tytso@mit.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mroth@nessie.de \
--cc=tytso@alum.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).