All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: What's in e2fsprogs.git (stable) -- E2fsprogs 1.41.0 released!
Date: Thu, 10 Jul 2008 18:02:34 -0400	[thread overview]
Message-ID: <20080710220234.GC3447@mit.edu> (raw)
In-Reply-To: <20080707213527.GV31490@mit.edu>

At long last, e2fsprogs 1.41.0 has been let loose on the world!  This
is the first stable/production version of e2fsprogs with ext4 support.

    		       	       	  	    	 - Ted

* The 'master' branch has these since the last announcement
  in addition to the above.

Andreas Dilger (1):
  blkid: Make regression test tolerate older versions of mkswap

Theodore Ts'o (13):
  debian: Add bash-static to the list of shells recommended for
      e2fsck-static
  Add a comment in INSTALL regarding --disable-tls on older systems
  mke2fs: Dumb down filesystems for GNU Hurd
  Fix incorrect definition of stripe-width in mke2fs man page
  badblocks: Use standard terminology for first/last block
  Don't use thread local storage if using diet libc
  mke2fs,tune2fs: Enable huge_file, dir_nlink, and extra_isize
      features
  resize2fs: Clean up the resize inode properly if necessary
  Update release checklist to include reminder to update translation
  Make ext2fs_check_desc() more stringent to force use of backup
      superbocks
  Update e2fsprogs.pot I18N translation template file
  Update dependencies in the Makefile for lib/ext2fs
  Update release notes, changelog, etc., for e2fsprogs 1.41 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-07-10 22:02 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                                   ` Theodore Tso [this message]
2008-08-23 16:51                                     ` 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

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=20080710220234.GC3447@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.