public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: New XFS git tree on oss.sgi.com
Date: Wed, 26 Nov 2008 15:08:40 +1100	[thread overview]
Message-ID: <20081126040840.GG6291@disturbed> (raw)
In-Reply-To: <492CC287.3070709@sgi.com>

On Wed, Nov 26, 2008 at 02:29:11PM +1100, Timothy Shimmin wrote:
> Dave Chinner wrote:
> > On Wed, Nov 26, 2008 at 12:00:41PM +1100, Lachlan McIlroy wrote:
> >> Christoph Hellwig wrote:
> >>> In either case, do you expect patches against the xfs-dev or the master
> >>> tree?  It would also be useful if the trees and which one to be used
> >>> could be documented on oss.sgi.com/projects/xfs or xfs.org.
> >> We would prefer patches based on the master branch but patches can be
> >> against the mainline, master or xfs-dev branches. If a patch against
> >> mainline or xfs-dev doesn't apply cleanly to the master branch we may
> >> ask the author to rebase that patch against the master branch. If a
> >> patch to the master branch needs auxillary changes to files that only
> >> exist in the xfs-dev branch (ie xfsidbg stuff) we may ask for an
> >> additional patch from the author.
> > 
> > IIUC correctly, you are saying that we'll have to provide two
> > different versions of every patch set? i.e. one that applies to
> > the -master branch and potentially another that applies to the
> > -xfs-dev branch?
> > 
> No, that's not how I was envisaging this.
> If you are not interested in modifying xfsidbg.c or dmapi
> then I'd expect you to only send patches against the master branch.

Ok, but that conflicts with "we may ask for an additional patch".

I'm trying to understand how we (i.e. those of us outside SGI) are
expected to use these branches. The new setup doesn't seem any
different to the old trees - there's one repository but really it is
still two "trees" that will require "external merging" to move
complex changes between them.

> I was expecting the xfs-team when they pull in or git-am the
> patches to update the other branch accordingly.

It might help to describe how you're expecting patches to flow
from the developers up to Linus - that might help us understand
how we should use these trees (i.e. describe the workflow you
expect to be using)....

Also, how does a "pull request" from a developer fit into this?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2008-11-26  4:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  7:22 New XFS git tree on oss.sgi.com Lachlan McIlroy
2008-11-25  8:16 ` Christoph Hellwig
2008-11-25 14:27   ` Russell Cattelan
2008-11-25 21:42     ` Mark Goodwin
2008-11-26  3:30       ` Christoph Hellwig
2008-11-26  3:36       ` Russell Cattelan
2008-11-26  1:03     ` Lachlan McIlroy
2008-11-26  1:17       ` Timothy Shimmin
2008-11-26  3:26       ` Russell Cattelan
2008-12-03  3:37         ` Niv Sardi
2008-12-09  9:17           ` Christoph Hellwig
2008-12-09 16:20             ` Russell Cattelan
2008-12-09 16:57               ` Christoph Hellwig
2008-12-09 17:12                 ` Russell Cattelan
2008-12-09 22:20               ` Niv Sardi
2008-12-10  0:07                 ` Russell Cattelan
2008-12-10  0:46                   ` Mark Goodwin
2008-12-10  1:14                   ` Niv Sardi
2008-12-10  6:51                 ` Christoph Hellwig
2008-11-26  3:30     ` Christoph Hellwig
2008-11-26  1:00   ` Lachlan McIlroy
2008-11-26  2:00     ` Dave Chinner
2008-11-26  3:29       ` Timothy Shimmin
2008-11-26  4:08         ` Dave Chinner [this message]
2008-11-26  5:41           ` Timothy Shimmin
2008-12-04 13:26             ` Christoph Hellwig
2008-12-05  3:29               ` Niv Sardi
2008-12-03  3:45           ` Niv Sardi
2008-11-26  3:28     ` Christoph Hellwig
2008-11-25 14:05 ` Christoph Hellwig
2008-11-26  1:11   ` Lachlan McIlroy
2008-11-26  3:27     ` Christoph Hellwig
2008-12-03  3:48       ` Niv Sardi
2008-12-03 13:04         ` Christoph Hellwig
2008-12-03 23:58           ` Niv Sardi
2008-12-04 12:34             ` Christoph Hellwig
2008-11-26  3:40 ` Eric Sandeen

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=20081126040840.GG6291@disturbed \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=tes@sgi.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