From: Ric Wheeler <rwheeler@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs 1.42-WIP-0702 released
Date: Mon, 04 Jul 2011 09:54:11 +0100 [thread overview]
Message-ID: <4E117FB3.3030403@redhat.com> (raw)
In-Reply-To: <E1QdWwc-0002Qx-Th@tytso-glaptop>
On 07/04/2011 01:23 AM, Theodore Ts'o wrote:
> I've made the first WIP release of e2fsprogs 1.42. The primary purpose
> is for people to test the 64-bit functionality and be confident that we
> didn't introduce any 32-bit regressions.
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/e2fsprogs-1.42-WIP-0702.tar.gz
>
> This has been built for Debian unstable, so we can get some initial
> testing.
>
> - Ted
Thanks Ted!
Do we have a specific idea of who is going to be testing and on what size file
systems?
We might want to see about getting this ready for Fedora as well at some point....
Ric
next prev parent reply other threads:[~2011-07-04 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 0:23 e2fsprogs 1.42-WIP-0702 released Theodore Ts'o
2011-07-04 8:54 ` Ric Wheeler [this message]
2011-07-04 17:49 ` Andreas Dilger
2011-07-04 17:52 ` Ric Wheeler
2011-08-09 13:10 ` Eric Sandeen
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=4E117FB3.3030403@redhat.com \
--to=rwheeler@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@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).