From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Nathan Scott <nscott@aconex.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH 00/20] xfs-cmds staging tree
Date: Mon, 29 Dec 2008 03:41:28 -0500 [thread overview]
Message-ID: <20081229084128.GA397@infradead.org> (raw)
In-Reply-To: <49585F70.5090709@sgi.com>
On Mon, Dec 29, 2008 at 04:26:08PM +1100, Mark Goodwin wrote:
> If we split it, we only loose the top level GNUmakefile, but gain the
> potential for separate maintainership (or even group write if needed)
> for each of the sub-projects. SGI can manage git/ptools for this easily
> enough internally.
>
> So the proposal would be to set up:
> git://oss.sgi.com/xfs/{acl,attr,xfstests,xfsprogs,xfsdump,dmapi,xfsmisc}.git
> as bare repositories, each with a 'master' and 'stable' branch (initially
> identical) and merge from master to stable whenever we want to release
> (and also grab tarballs to preserve Barry's previous release process until
> such time as the distros catch on).
>
> Before I go and do this, note we already have Russell's ptools/cvs
> mirror at git://oss.sgi.com/xfs-cmds which has the advantage of some
> history. Would we want to keep any of that history? Since this already
> mirrors t-o-t ptools, I could just as easily take a clone of that as
> git://oss.sgi.com/xfs/xfs-cmds.git and be done with it. Opinions?
I've setup a few experimental trees:
http://git.kernel.org/?p=fs/xfs/acl.git;a=summary
http://git.kernel.org/?p=fs/xfs/attr.git;a=summary
http://git.kernel.org/?p=fs/xfs/dmapi.git;a=summary
http://git.kernel.org/?p=fs/xfs/nfs4acl.git;a=summary
http://git.kernel.org/?p=fs/xfs/xfsdump.git;a=summary
http://git.kernel.org/?p=fs/xfs/xfsprogs.git;a=summary
http://git.kernel.org/?p=fs/xfs/xfstests.git;a=summary
which do import all the history from the public CVS tree. Unlike the
git tree on oss.sgi.com it does this in a nicer way by hacking cvsps to
actually detect ptool changest properly insted of splitting them into
multiple git commits due to the different per-file comments, having a
mapping from sgi login IDs to proper real names and having a single
import instead of multiple import and their merges.
The only real problem with these is that the CVS tree hasn't been
updated since October (and I've missed a few names on my first round of
imports).
I think these should be used as a model for the future trees, we can
have these kernel.org trees for the community (current Eric, Dave and me
could commit to those about, and we should add Nathan and Andreas soon),
and then sgi can pull them into their trees for official releases or
product trees.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-29 8:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 16:38 [PATCH 00/20] xfs-cmds staging tree Christoph Hellwig
2008-12-22 16:38 ` [PATCH 01/20] fix up xfs-cmds build after the parallel-fest Christoph Hellwig
2008-12-22 16:38 ` [PATCH 02/20] update Debian packaging Christoph Hellwig
2008-12-22 16:38 ` [PATCH 03/20] Fix build when gettext is enabled Christoph Hellwig
2008-12-22 16:38 ` [PATCH 04/20] Apply gettext translation to strings kept in format->{fmt, msg, type} Christoph Hellwig
2008-12-22 16:38 ` [PATCH 05/20] xfsprogs Polish translation update Christoph Hellwig
2008-12-22 16:38 ` [PATCH 06/20] build system: Make --enable-gettext actually enable gettext Christoph Hellwig
2008-12-22 16:38 ` [PATCH 07/20] return error status from the xfs_quota tool Christoph Hellwig
2008-12-22 16:38 ` [PATCH 08/20] xfs_quota: Add missing options to --help Christoph Hellwig
2008-12-22 16:38 ` [PATCH 09/20] xfs_quota: Fix range for -U Christoph Hellwig
2008-12-22 16:38 ` [PATCH 10/20] xfs_quota: Warn if specified non-zero quota will be round down to zero Christoph Hellwig
2008-12-22 16:38 ` [PATCH 11/20] xfs_quota: Dont ignore every error when asking for quota Christoph Hellwig
2008-12-22 16:38 ` [PATCH 12/20] EXCLUDED_FILE_TYPES: Fix macro for negation case Christoph Hellwig
2008-12-22 16:38 ` [PATCH 13/20] xfstests: test 194, test tricky mapping/conversion around holes Christoph Hellwig
2008-12-22 16:38 ` [PATCH 14/20] xfstests: add a unified diff option Christoph Hellwig
2008-12-22 16:38 ` [PATCH 15/20] fix xfsqa 189 for log and rt devices Christoph Hellwig
2008-12-22 16:38 ` [PATCH 16/20] xfstests: fix dbtest build Christoph Hellwig
2008-12-22 16:38 ` [PATCH 17/20] xfstests: add more tests to the auto group Christoph Hellwig
2008-12-22 16:38 ` [PATCH 18/20] 080 seems to run fine on linux, un-comment the quiet var to make the output match. Added to auto group as well Christoph Hellwig
2008-12-22 16:38 ` [PATCH 19/20] xfsdump: add support for building with sparse Christoph Hellwig
2008-12-22 16:38 ` [PATCH 20/20] xfsprogs: resync libxfs with the kernel code Christoph Hellwig
2008-12-30 17:39 ` Christoph Hellwig
2009-01-22 20:15 ` Christoph Hellwig
2008-12-22 20:33 ` [PATCH 00/20] xfs-cmds staging tree Mark Goodwin
2008-12-22 20:49 ` Christoph Hellwig
2008-12-22 22:11 ` Mark Goodwin
2008-12-22 22:16 ` Christoph Hellwig
2008-12-22 23:02 ` Nathan Scott
2008-12-29 5:26 ` Mark Goodwin
2008-12-29 8:41 ` Christoph Hellwig [this message]
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=20081229084128.GA397@infradead.org \
--to=hch@infradead.org \
--cc=markgw@sgi.com \
--cc=nscott@aconex.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