linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: linux-ext4@vger.kernel.org
Subject: The pu branch of e2fsprogs also updated
Date: Thu, 11 Feb 2010 02:30:18 -0500	[thread overview]
Message-ID: <20100211073018.GH739@thunk.org> (raw)
In-Reply-To: <E1NfLwx-00062Q-AX@closure.thunk.org>

I've also updated the "pu", or "proposed updates" branch of e2fsprogs
to have my latest spin of the 64-bit patches.  They are nearly
completely cleaned up now, but they're not quite there yet.  Since I
need to context switch to getting kernel patches out the door, I
thought this would be a good time to update the pu branch.

The pu branch is now rebased against the latest 1.41.10 release, and
the remaining patches have been largely refactored.  The two patches
that still need a bit of cleanup and review are:

libext2fs: More random 64-bit fixes, lots of block_iterate3

and

Fix bug in selecting fs type, resulting in 1K blocksize

Otherwise, the patches have been refactored, the ABI breakage fixed,
and some API's cleaned up.  There are only a "bakers dozen" of patches
that still need to be merged into the mainline branch, so hopefully
the rest of cleanup will get done soon after I get the ext4 kernel
patch queue under control and ready for the merge window.

      	    	  	      	    	    - Ted

  reply	other threads:[~2010-02-11  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 23:26 E2fsprogs 1.41.10 has been released Theodore Ts'o
2010-02-11  7:30 ` tytso [this message]
2010-02-11 16:54 ` tytso
2010-02-12  6:22 ` Nikola Ciprich
2010-02-12 16:27   ` tytso

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=20100211073018.GH739@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).