From: Mark Tinguely <tinguely@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "'linux-xfs@oss.sgi.com'" <linux-xfs@oss.sgi.com>
Subject: Re: Time for an xfsprogs "alpha1" release?
Date: Thu, 12 Sep 2013 16:54:22 -0500 [thread overview]
Message-ID: <5232380E.4040300@sgi.com> (raw)
In-Reply-To: <52322F7A.8060405@sandeen.net>
On 09/12/13 16:17, Eric Sandeen wrote:
> With all of the changes for CRC filesystems in xfsprogs git now, I'm wondering if it'd be a good idea to do a "3.2.0-alpha1" sort of release.
>
> I know it's not yet feature complete, but I think there would be value in getting a version-stamped tarball out there for testing - it could filter to rawhide-ish distros, and get a bit more airtime while the remaining bits get worked out.
>
> We'd probably want a nice readme about what's new and what's not yet done, caveats, etc, but I think it'd be worth getting it out there into the hands of willing testers, w/o requiring them to do a build from git.
>
> Thoughts?
>
> Thanks,
> -Eric
>
Good idea, but xfsprogs is in a state that it can't compile:
http://oss.sgi.com/archives/xfs/2013-09/msg00396.html
Patch 31 v3 / 55 is broken. It is missing xfs_sb.c and has an extra
xfs_mount.c.
If you want it this week, we could do the corrections or wait for Dave
to repost.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-12 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 21:17 Time for an xfsprogs "alpha1" release? Eric Sandeen
2013-09-12 21:38 ` Greg Freemyer
2013-09-12 21:54 ` Mark Tinguely [this message]
2013-09-12 22:18 ` Eric Sandeen
2013-09-12 23:40 ` Mark Tinguely
2013-09-13 1:58 ` 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=5232380E.4040300@sgi.com \
--to=tinguely@sgi.com \
--cc=linux-xfs@oss.sgi.com \
--cc=sandeen@sandeen.net \
/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.