From: Ben Myers <bpm@sgi.com>
To: xfs@oss.sgi.com
Subject: userspace release -rc2
Date: Thu, 29 Nov 2012 16:47:14 -0600 [thread overview]
Message-ID: <20121129224714.GK27055@sgi.com> (raw)
Hi,
I've marked -rc2 for the userspace releases as a conversation starter. See:
git://oss.sgi.com/xfs/cmds/dmapi.git v2.2.11-rc2
git://oss.sgi.com/xfs/cmds/xfsdump.git v3.1.1-rc2
git://oss.sgi.com/xfs/cmds/xfsprogs.git v3.1.9-rc2
git://oss.sgi.com/xfs/cmds/xfstests.git v1.2.0-rc2
I believe many of the items on our list from -rc1 have been resolved.
1) xfsdump header checksum failures, fixed by b7af332.
2) futex hang in 059, still pending
3) the golden output changes related to multistream support in xfsdump
and --largefs, fixed in the dump filter in Dave's --largefs patchset
4) test on more platforms
AFAIK the futex hang has not been seen recently so we might not want to
hold the release for that. Maybe there are some stragglers on the
mailing list to pull in. If there are additional items for the todo
list, speak up! ;)
Thanks,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-11-29 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 22:47 Ben Myers [this message]
2012-11-29 23:13 ` userspace release -rc2 Mark Tinguely
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=20121129224714.GK27055@sgi.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox