All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ben Myers <bpm@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs v3.1.7
Date: Sat, 19 Nov 2011 12:51:02 -0500	[thread overview]
Message-ID: <20111119175102.GA3334@infradead.org> (raw)
In-Reply-To: <20111117233139.GL29840@sgi.com>

On Thu, Nov 17, 2011 at 05:31:39PM -0600, Ben Myers wrote:
> Version 3.1.7 of xfsprogs has been released.

Can we please avoid totally uncoordinated and rushed release in
the future?  You personally had quetions about the lost+found
nlink issues that still haven't been resolved, and there's tons
of repair fixes that should have made it int othe next release.

If we only have a tiny debian specific fixup we should have a
Debian-specific branch with just that one liner.  Real releases
with actual changes need QA and coordination.

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

  reply	other threads:[~2011-11-19 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 23:31 [ANNOUNCE] xfsprogs v3.1.7 Ben Myers
2011-11-19 17:51 ` Christoph Hellwig [this message]
2011-11-21 15:40   ` Ben Myers
2011-11-22  0:16     ` Dave Chinner

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=20111119175102.GA3334@infradead.org \
    --to=hch@infradead.org \
    --cc=bpm@sgi.com \
    --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 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.