From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 23732] ext4 timestamp range contains 68-year gaps
Date: Sat, 21 Feb 2015 01:15:57 +0000 [thread overview]
Message-ID: <bug-23732-13602-q4BrabpsG4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-23732-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=23732
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |tytso@mit.edu
Resolution|CODE_FIX |---
--- Comment #10 from Theodore Tso <tytso@mit.edu> ---
I'm not sure why the test cases have been passing but the true fix hasn't been
applied yet. This is due to my not having time and the need for us to have
better test cases in e2fsprogs (for both the old and new encodings, etc.) As
usual, the highly urgent problems with short-term deadlines tend to get higher
priority from the important long-term items.
Specifically, I want to be able to convert time strings to integers using both
the old the new encodings, and then have test cases to make sure that e2fsck
and the kernel are doing the right thing and coverting as necessary as we had
determined in the migration plan for this bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-02-21 1:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 11:28 [Bug 23732] New: ext4 timestamp range contains 68-year gaps bugzilla-daemon
2012-08-14 13:40 ` [Bug 23732] " bugzilla-daemon
2014-03-30 13:47 ` bugzilla-daemon
2014-03-30 15:08 ` bugzilla-daemon
2014-03-30 15:18 ` bugzilla-daemon
2014-03-30 15:19 ` bugzilla-daemon
2014-04-01 3:32 ` bugzilla-daemon
2015-02-19 16:01 ` bugzilla-daemon
2015-02-20 20:01 ` Andreas Dilger
2015-02-19 16:15 ` bugzilla-daemon
2015-02-19 19:22 ` bugzilla-daemon
2015-02-19 20:16 ` bugzilla-daemon
2015-02-19 20:18 ` bugzilla-daemon
2015-02-21 1:15 ` bugzilla-daemon [this message]
2016-03-20 16:54 ` bugzilla-daemon
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=bug-23732-13602-q4BrabpsG4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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