From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Re: Release candidate for e2fsprogs 1.42.7
Date: Thu, 17 Jan 2013 14:52:01 -0500 [thread overview]
Message-ID: <20130117195201.GA477@thunk.org> (raw)
In-Reply-To: <nsx1udkewcz.fsf@closure.thunk.org>
On Wed, Jan 16, 2013 at 02:55:24PM -0500, Theodore Ts'o wrote:
> Hi all,
>
> I've just pushed an update to the e2fsprogs maint repository, and commit
> 8359f626a4e9 (the tip of the maint branch) is a release candidate for
> 1.42.7. Please give it a test! If I don't get any show-stopping bug
> reports, I plan to release it as 1.42.7 in the day or two.
I screwed up and didn't do the final push to git.kernel.org. So the
maint branch didn't have the most recent commit (8359f626a4e9, dated
January 16th) until just a few minutes ago.
Sorry about that. I'll give folks another day to test things out.
- Ted
prev parent reply other threads:[~2013-01-17 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 19:55 Release candidate for e2fsprogs 1.42.7 Theodore Ts'o
2013-01-17 19:52 ` Theodore Ts'o [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=20130117195201.GA477@thunk.org \
--to=tytso@mit.edu \
--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).