From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: New e2fsprogs release?
Date: Tue, 13 Sep 2011 10:17:39 -0500 [thread overview]
Message-ID: <4E6F7413.7030906@redhat.com> (raw)
It's approaching a year since the last e2fsprogs release, 1.41.14, with hundreds of commits since then.
a "WIP" release was made a few months ago in July, containing much of the 64-bit support.
I've put this WIP release into Fedora Rawhide, and I've had no complaints yet.
I'd like to get a little visibility into when 1.42 may be released, or what must be completed for this to be done. I'd rather not ship F17 with a "WIP" release of a core package like this, if possible.
Ted, can you offer any guidance or insight?
Thanks,
-Eric
p.s. Would it be possible to retroactively tag v1.42-WIP-0702 in the tree?
reply other threads:[~2011-09-13 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E6F7413.7030906@redhat.com \
--to=sandeen@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.