public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Gabriel Vlasiu <gabrielvlasiu@gmail.com>,
	nathans@debian.org, xfs@oss.sgi.com
Subject: pushing out a new xfsprogs release, was Re: [PATCH] xfsprogs: fix unaligned access in libxfs
Date: Fri, 28 Aug 2009 14:24:54 -0400	[thread overview]
Message-ID: <20090828182454.GA8217@infradead.org> (raw)
In-Reply-To: <4A9810C7.8010806@sandeen.net>

On Fri, Aug 28, 2009 at 10:15:51AM -0700, Eric Sandeen wrote:
> Looks good to me.
>
> Reviewed-by: Eric Sandeen <sandeen@sandeen.net>

Thanks.  What do people thing about pushing out a 3.0.3 xfsprogs
release?

Since 3.0.1 (discounting 3.0.2 as a Debian-only thing quickly following
3.0.1): we have the following changes the list below.  It's not a whole
lot, but everything is relatively small fixes, the the unaligned thing
makes the 3.0 series so far unusable on strict alignment platforms.

If we go for it I can update the CHANGES ASAP for the release, and
ater that we can start putting in changes for a 3.1.0 release - I have
Barry's repair speedups ready for a wider audience, Eric has the
patch to make the lazy sb counters default and I can do the long
needed resync with the kernel code.


Changes from 3.0.1 to HEAD:



Christoph Hellwig (3):
      add release.sh
      Merge branch 'master' of git://oss.sgi.com/xfs/cmds/xfsprogs
      xfsprogs: fix unaligned access in libxfs

David Chinner (1):
      mkfs: allow to make larger logs

Eric Sandeen (11):
      xfsprogs: fix readline/editline for xfs_io and xfs_quota
      xfs_io: add fallocate command
      Update CHANGES file for recent commits
      xfs_repair: catch bad depth in traverse_int_dir2block
      xfs_io: fix test for fallocate on 32bit boxes
      xfs_repair: fix agcount*agblocks overflows
      xfs_metadump: agcount*agblocks overflow
      xfs_repair: clear inodes in incorrect btree format
      the freesp doesn't support "-f" so take it out of the usage().
      xfs_db: do bounds checking in frag's scanfunc_bmap
      xfs_io: actually issue 0 size writes

Felix Blyakher (2):
      Merge branch 'master' of git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev
      3.0.1 release

Nathan Scott (2):
      Resolve minor man page warnings reported by lintian tool.
      Debian packaging updates, and bumped minor version to 3.0.2.

Nathaniel W. Turner (1):
      xfs_repair: open filesystem device exclusively

Robert Herndon (1):
      add -x flags to include/install-sh

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-08-28 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28 15:37 [PATCH] xfsprogs: fix unaligned access in libxfs Christoph Hellwig
2009-08-28 17:15 ` Eric Sandeen
2009-08-28 18:24   ` Christoph Hellwig [this message]
2009-08-28 21:20     ` pushing out a new xfsprogs release, was " Felix Blyakher
2009-08-29 22:17     ` Michael Monnerie
2009-08-30  1:22       ` Eric Sandeen
2009-08-30  8:44         ` Michael Monnerie
2009-08-28 21:39 ` Alex Elder
2009-08-28 22:15   ` Christoph Hellwig
2009-08-28 22:38     ` Alex Elder

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=20090828182454.GA8217@infradead.org \
    --to=hch@infradead.org \
    --cc=gabrielvlasiu@gmail.com \
    --cc=nathans@debian.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /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