From: Theodore Tso <tytso@mit.edu>
To: "Hanno Böck" <ml@hboeck.de>
Cc: linux-ext4@vger.kernel.org, Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: E2fsprogs 1.40 release imminent!
Date: Fri, 29 Jun 2007 21:04:35 -0400 [thread overview]
Message-ID: <20070630010435.GE32178@thunk.org> (raw)
In-Reply-To: <200706292351.33006.ml@hboeck.de>
On Fri, Jun 29, 2007 at 11:51:29PM +0200, Hanno Böck wrote:
> Am Montag 25 Juni 2007 schrieb Theodore Ts'o:
> > ... contains what I hope to be the e2fsprogs 1.40 release. If folks
> > could test it and let me know if they find any embarassing bugs, I would
> > greatly appreciate it. It can also be found at:
>
> There are a bunch of patches applied in the gentoo package that might be worth
> looking at:
> http://dev.gentoo.org/~hanno/e2fsprogs/
>
> All of them still seem to apply to the current mercurial source. I'm not
> really familiar with them, just noted that there are a lot of patches and
> nobody seemed to care sending upstream in the past.
>
> e2fsprogs-1.32-mk_cmds-cosmetic.patc
> e2fsprogs-1.38-tests-locale.patch
> e2fsprogs-1.39-makefile.patch
> e2fsprogs-1.39-parse-types.patch
> e2fsprogs-1.39-util-strptime.patch
> e2fsprogs-1.40-libintl.patch
Thanks, none of these are critical. I'll go through them and apply
them after the 1.40 release.
e2fsprogs-1.39-util-strptime.patch was fixed in another way in my
sources.
- Ted
prev parent reply other threads:[~2007-06-30 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 22:12 E2fsprogs 1.40 release imminent! Theodore Ts'o
2007-06-24 23:11 ` Lennert Buytenhek
2007-06-25 15:38 ` [PATCH] e2fsprogs: Add undo I/O manager [ Was Re: E2fsprogs 1.40 release imminent! ] Aneesh Kumar K.V
2007-06-25 19:03 ` Theodore Tso
2007-06-29 21:51 ` E2fsprogs 1.40 release imminent! Hanno Böck
2007-06-30 1:04 ` 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=20070630010435.GE32178@thunk.org \
--to=tytso@mit.edu \
--cc=buytenh@wantstofly.org \
--cc=linux-ext4@vger.kernel.org \
--cc=ml@hboeck.de \
/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.