From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Jan Engelhardt <jengelh@inai.de>, Christoph Hellwig <hch@lst.de>,
xfs@oss.sgi.com
Subject: Re: status of userspace release
Date: Mon, 29 Oct 2012 11:17:22 -0500 [thread overview]
Message-ID: <20121029161722.GF31970@sgi.com> (raw)
In-Reply-To: <20121028212708.GK29378@dastard>
Hi Dave,
On Mon, Oct 29, 2012 at 08:27:08AM +1100, Dave Chinner wrote:
> On Fri, Oct 26, 2012 at 04:57:41PM -0500, Ben Myers wrote:
> > Hi,
> >
> > On Thu, Oct 25, 2012 at 10:15:01AM -0500, Ben Myers wrote:
> > > We're working toward a userspace release this month. There are several patches
> > > that need to go in first, including backing out the xfsdump format version bump
> > > from Eric, fixes for the makefiles from Mike, and the Polish language update
> > > for xfsdump from Jakub. If anyone knows of something else we need, now is the
> > > time to flame about it. I will take a look around for other important patches
> > > too.
> > >
> > > This time I'm going to tag an -rc1 (probably later today or tomorrow). We'll
> > > give everyone a few working days to do a final test and/or pipe up if we have
> > > missed something important. Then if all goes well we'll cut the release next
> > > Tuesday.
> >
> > I've tagged -rc1 for the upcoming releases of dmapi, xfsprogs, and xfsdump. If
> > we missed something important now is the time to speak up.
> >
> > Currently there are two items of which I'm aware:
> >
> > 1) the Polish (and German) translations of xfsdump are not working. I'll start
> > a separate thread for that issue.
> >
> > 2) Christoph has pointed out this patch series:
> >
> > http://oss.sgi.com/archives/xfs/2012-05/msg00323.html
> > http://oss.sgi.com/archives/xfs/2012-10/msg00541.html
>
> I agree with christoph - the kernel side intptr/uintptr stuff that
> Jan did needs to go into the kernel first, and then brought to
> libxfs via a kernel code sync. A kernel code resync needs to be
> done immediately after the xfsprogs release so that usrspace is
> using the same base code for the CRC work, so splitting them to
> before/after the relases makes sense IMO....
Sounds good. I'll pull in 2, 3, and 6 for now.
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-29 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 15:15 status of userspace release Ben Myers
2012-10-26 21:57 ` Ben Myers
2012-10-28 21:27 ` Dave Chinner
2012-10-29 16:17 ` Ben Myers [this message]
2012-11-02 5:51 ` Dave Chinner
2012-11-02 18:59 ` Ben Myers
2012-11-02 23:03 ` Dave Chinner
2012-11-03 0:16 ` Dave Chinner
2012-11-03 1:35 ` Eric Sandeen
2012-11-03 1:55 ` Dave Chinner
2012-11-03 3:16 ` Dave Chinner
2012-11-03 1:53 ` 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=20121029161722.GF31970@sgi.com \
--to=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jengelh@inai.de \
--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.