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: Christoph Hellwig <hch@infradead.org>,
	Mike Frysinger <vapier@gentoo.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsprogs/xfsdump release process
Date: Tue, 24 Feb 2009 08:20:04 -0500	[thread overview]
Message-ID: <20090224132003.GC1579@infradead.org> (raw)
In-Reply-To: <49A2F933.3090308@sandeen.net>

On Mon, Feb 23, 2009 at 01:29:55PM -0600, Eric Sandeen wrote:
> Just FWIW, Fedora does similar.  Changing md5sums on a released,
> versioned tarball could set off all sorts of worries for distributions,
> in general...

Yeah.  Guys, what about declaring the 3.0.0 releases officially botched
and get 3.0.1 out next week?  That should include all the small fixes
we have out now and whatever small stuff comes up from distros trying
to use it.

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

  reply	other threads:[~2009-02-24 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 18:48 dmapi-2.2.9 release Mike Frysinger
2009-02-22 20:39 ` xfsprogs/xfsdump release process Mike Frysinger
2009-02-23  5:00   ` Felix Blyakher
2009-02-23  7:22     ` Christoph Hellwig
2009-02-23 16:10       ` Felix Blyakher
2009-02-23 16:25         ` Mike Frysinger
2009-02-23 16:38           ` Felix Blyakher
2009-02-23 19:29             ` Eric Sandeen
2009-02-24 13:20               ` Christoph Hellwig [this message]
2009-02-24 15:05   ` Mike Frysinger
2009-02-24 18:44     ` Christoph Hellwig
2009-02-24 19:06       ` Mike Frysinger

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=20090224132003.GC1579@infradead.org \
    --to=hch@infradead.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