All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Re: What's in e2fsprogs.git (stable)
Date: Mon, 13 Oct 2008 00:09:27 -0400	[thread overview]
Message-ID: <20081013040927.GK12662@mit.edu> (raw)
In-Reply-To: <20081002134139.GB25164@mit.edu>

I've just released e2fsprogs 1.41.3 to fix a few more bug fixes, and
to smooth the transition from ext4dev to ext4, which will occur in
2.6.28.  Distributions that are contemplating releasing e2fsprogs
1.41.x are strongly recommended to use e2fsprogs 1.41.3.

* The 'maint' and 'master' branches have these fixes since the last
  announcement:

Eric Sandeen (4):
  e2fsprogs: fix blkid detection of ext4dev as ext4
  unix_io: check for read-only devices when opening R/W
  resize2fs: check for bogus new_size
  e2fsck: exit from preenhalt if IO errors were encountered

Theodore Ts'o (8):
  Update Makefile depend information for crc16.o
  Fix parallel build problem with util/subst
  debugfs: Fix ncheck when printing pathnames for multiple hardlinks
      in a directory
  libblkid: Fix file descriptor leak when checking for a module
  e2fsck: Print the correct inode number for uninit-bg related
      problem reports
  e2fsck: Offer to clear the test_fs flag if ext4 is available
  Update e2fsprogs translation template file
  Update release notes, changelog, etc., for e2fsprogs 1.41.3 release

------
URL's for the e2fsprogs repository:
	git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
	http://www.kernel.org/pub/scm/fs/ext2/e2fsprogs.git

      reply	other threads:[~2008-10-13  4:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04 22:43 What's in e2fsprogs.git (stable) Theodore Ts'o
2007-12-17 17:11 ` Theodore Ts'o
2007-12-17 17:23   ` Jan Kara
2007-12-17 20:48     ` Theodore Tso
2008-01-01 18:01   ` Theodore Tso
2008-02-11  4:41     ` Theodore Tso
2008-02-11 20:54       ` Andreas Dilger
2008-02-19  5:03       ` Theodore Tso
2008-02-29 14:28         ` Theodore Tso
2008-02-29 16:19           ` Eric Sandeen
2008-02-29 16:35             ` Theodore Tso
2008-03-13 18:05           ` Theodore Tso
2008-03-20 20:22             ` Theodore Tso
2008-04-02  0:06               ` Theodore Tso
2008-04-07 16:55                 ` Theodore Tso
2008-04-18 18:39                   ` Theodore Tso
2008-04-21 16:27                     ` Theodore Tso
2008-04-28  2:53                       ` Theodore Tso
2008-05-24 23:49                         ` Theodore Tso
2008-06-03  2:39                           ` Theodore Tso
2008-06-08  2:41                             ` Theodore Tso
2008-06-17 12:05                               ` Theodore Tso
2008-07-07 21:35                                 ` Theodore Tso
2008-07-10 22:02                                   ` What's in e2fsprogs.git (stable) -- E2fsprogs 1.41.0 released! Theodore Tso
2008-08-23 16:51                                     ` What's in e2fsprogs.git (stable) Theodore Tso
2008-08-28  3:37                                       ` Theodore Tso
2008-09-01 20:57                                         ` Theodore Tso
2008-10-02 13:41                                           ` Theodore Tso
2008-10-13  4:09                                             ` 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=20081013040927.GK12662@mit.edu \
    --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 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.