[Top] [All Lists]

Re: projid32bit=1 default in xfsprogs-3.2.0

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: projid32bit=1 default in xfsprogs-3.2.0
From: Ben Myers <bpm@xxxxxxx>
Date: Tue, 15 Oct 2013 16:49:10 -0500
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20131015213110.GA5895@xxxxxxxxxxxxx>
References: <525C1C15.7020204@xxxxxxxxxxx> <20131014211659.GI5663@dastard> <20131014212347.GB1935@xxxxxxx> <525C6108.6010108@xxxxxxxxxxx> <20131015194609.GC32095@xxxxxxxxxxxxx> <20131015204342.GA24997@xxxxxxxxxxxxx> <20131015212214.GC1935@xxxxxxx> <20131015213110.GA5895@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)

On Tue, Oct 15, 2013 at 02:31:10PM -0700, Christoph Hellwig wrote:
> On Tue, Oct 15, 2013 at 04:22:14PM -0500, Ben Myers wrote:
> > The tags are out there:
> > http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfsprogs.git;a=tags
> I managed to somehow miss them.  Sorry!

> > That's an interesting idea.  We hadn't discussed a 3.1.12 release.  No
> > particular objection to doing that, it's just that we didn't branch for the
> > v3.0.5->v3.1.0 set of releases.  Maybe it is better if we all focus on 
> > 3.2.0.
> With git you can easily branch from a past commit, e.g.:
> hch@brick:~/work/xfsprogs$ git checkout -b release-3.1 v3.1.11
> Switched to a new branch 'release-3.1'

Yep.  If folks want a 3.1.12 we should certainly kick the idea around a bit.
I'm just guessing that most would prefer to focus on a 3.2.0 in the near term.
Maybe I'm mistaken about that though.  ;)


<Prev in Thread] Current Thread [Next in Thread>