From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Scott James Remnant <scott@ubuntu.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsck: Always fix last mount/write/check time with -p
Date: Wed, 21 Oct 2009 18:20:58 -0400 [thread overview]
Message-ID: <20091021222058.GD20619@mit.edu> (raw)
In-Reply-To: <4AD9E15D.2060400@redhat.com>
On Sat, Oct 17, 2009 at 10:23:09AM -0500, Eric Sandeen wrote:
>> From ba5131f6d48eded504e84c2a8ffc8131df8a512e Mon Sep 17 00:00:00 2001
>> From: Theodore Ts'o <tytso@mit.edu>
>> Date: Fri, 16 Oct 2009 20:46:45 -0400
>> Subject: [PATCH] e2fsck: Accept superblock times to be fudged by up to 24 hours by default
>
> could you please push this out to the kernel.org repo?
Done, sorry for the delay.
- Ted
prev parent reply other threads:[~2009-10-21 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 15:10 [PATCH] e2fsck: Always fix last mount/write/check time with -p Scott James Remnant
2009-10-12 15:44 ` Eric Sandeen
2009-10-12 23:41 ` Andreas Dilger
2009-10-17 1:03 ` Theodore Tso
2009-10-17 15:23 ` Eric Sandeen
2009-10-21 22:20 ` 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=20091021222058.GD20619@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=scott@ubuntu.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).