public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, nathans@debian.org, vapier@gentoo.org,
	sandeen@sandeen.net
Subject: xfsprogs 3.0.5 "release"
Date: Sun, 25 Oct 2009 03:03:31 -0400	[thread overview]
Message-ID: <20091025070331.GA21120@infradead.org> (raw)

It looks like SGI rushed out a 3.0.5 xfsprogs release which contains
various half-cooked changes including additions to shared libraries
without bumping the minor version and wrong patch attributions.

I can only recommend to not pick it up for distributions and wait for a
proper release from the kernel.org trees after the full release
engineering process has finished.  The current plan is to have a release
end of Novemeber, we'll have to figure out the naming / numbering to not
clash with the SGI versions.

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

             reply	other threads:[~2009-10-25  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25  7:03 Christoph Hellwig [this message]
2009-10-26 22:37 ` xfsprogs 3.0.5 "release" Eric Sandeen

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=20091025070331.GA21120@infradead.org \
    --to=hch@infradead.org \
    --cc=nathans@debian.org \
    --cc=sandeen@sandeen.net \
    --cc=vapier@gentoo.org \
    --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