public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 00/20] xfs-cmds staging tree
Date: Tue, 23 Dec 2008 09:11:46 +1100	[thread overview]
Message-ID: <495010A2.2030903@sgi.com> (raw)
In-Reply-To: <20081222204956.GA23453@infradead.org>



Christoph Hellwig wrote:
> On Tue, Dec 23, 2008 at 07:33:55AM +1100, Mark Goodwin wrote:
>>
>> Christoph Hellwig wrote:
>>> This is the staging tree of xfs patches.  Given that Barry is gone now it seem
>>> like no one cares about userspace and I'll play patch monkey for now.
>> Thanks Christoph. Lachlan and I were just discussing yesterday that
>> it's time to set up a git repository for xfs-cmds on oss. This would
>> contain all the userspace stuff: attr, acl, xfsprogs, dmapi, xfsdump
>> and xfstests.
>>
>> Anyone have a reason not to keep all of this together in the one tree?
>> I guess we'd need branches for 'master' (aka dev) and 'stable' or
>> something ..?
>
> Yes, that's a plan.  Can you set it up in a way that we can push
> directly to, similar to how Nathan does it for pcp?

I unsure, but don't think a group writable repository would work too well.
Nathan doesn't push directly into the official pcp git tree (which is at
git://oss/pcp/pcp.git) but rather pushes to his own git tree (which is
at git://oss/nathans/pcp.git). SGI review and pull those commits and push
them into the official tree (via an internal staging tree using a hook
for the ptools back-end, but that's transparent to oss users). Nathan also
reviews patches from others and pulls their patches into his tree, and
regularly re-syncs with the official tree. git works it all out just fine.

This is fairly new, but seems to work rather well since it supports
effective collaboration for trusted contributors without SGI becoming
a patch acceptance bottleneck - sort of a multiple maintainership.

> Nathan would also like to push to the xfs-cmds tree for the debian packaging, btw.

ok

> One thing we were discussing is if it's really a good idea to have all
> these together.

It would certainly help SGI if the directory structure for the proposed
xfs-cmds tree remained the same as it is in ptools at the moment. I
guess we could consider splitting each xfs-cmds directory into separate
repositories, but then building it all togetheer would be a pain. It could
certainly make sense to split off xfstests into it's own tree since it's
not part of the xfs-cmds build.

Cheers
- Mark

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2008-12-22 22:12 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 [this message]
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

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=495010A2.2030903@sgi.com \
    --to=markgw@sgi.com \
    --cc=hch@infradead.org \
    --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