From: Rich Johnston <rjohnston@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [RFC] Userspace and xfstests releases
Date: Thu, 19 Dec 2013 11:29:04 -0600 [thread overview]
Message-ID: <52B32CE0.5070701@sgi.com> (raw)
In-Reply-To: <52B06E51.1020504@sgi.com>
On 12/17/2013 09:31 AM, Rich Johnston wrote:
> I was planning on a xfsdump and xfstests release this week before I go
> on vacation. Any objections?
Currently xfstests is not released, should this be changed?
I will wait until I return on Jan 2 to release xfsprogs.
>
> Release versions for xfsprogs are still being discussed. Are there any
> more comments on this subject?
Here is one of the threads discussing this.
http://oss.sgi.com/archives/xfs/2013-10/msg00421.html
Christoph were you saying you create xfsprogs branches?
Is there a consensus on version names/branches for xfsprogs?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-19 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 15:31 [RFC] Userspace and xfstests releases Rich Johnston
2013-12-19 17:29 ` Rich Johnston [this message]
2013-12-19 19:33 ` Ben Myers
2013-12-19 22:04 ` Dave Chinner
2013-12-26 8:56 ` Christoph Hellwig
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=52B32CE0.5070701@sgi.com \
--to=rjohnston@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox