xfs
[Top] [All Lists]

Re: projid32bit=1 default in xfsprogs-3.2.0

To: Ben Myers <bpm@xxxxxxx>
Subject: Re: projid32bit=1 default in xfsprogs-3.2.0
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 15 Oct 2013 14:31:10 -0700
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20131015212214.GC1935@xxxxxxx>
References: <525C1C15.7020204@xxxxxxxxxxx> <20131014211659.GI5663@dastard> <20131014212347.GB1935@xxxxxxx> <525C6108.6010108@xxxxxxxxxxx> <20131015194609.GC32095@xxxxxxxxxxxxx> <20131015204342.GA24997@xxxxxxxxxxxxx> <20131015212214.GC1935@xxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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'

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