public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Cattelan <cattelan@thebarn.com>
To: markgw@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: New XFS git tree on oss.sgi.com
Date: Tue, 25 Nov 2008 21:36:29 -0600	[thread overview]
Message-ID: <492CC43D.8020704@xfs.org> (raw)
In-Reply-To: <492C7160.80208@sgi.com>

Mark Goodwin wrote:
>
>
> Russell Cattelan wrote:
>> Christoph Hellwig wrote:
>>> On Tue, Nov 25, 2008 at 06:22:21PM +1100, Lachlan McIlroy wrote:
>>>
>>>> There's a few branches there already:
>>>>
>>>> 'master'      This will contain all the latest xfs changes not yet 
>>>> pushed
>>>>                to mainline.
>>>> 'mainline'    This is vanilla mainline and will updated regularly.
>>>> 'for-linus'   Our staging branch for pull requests
>>>> 'xfs-dev'     This branch will contain KDB and other supporting 
>>>> code for
>>>>                development and should be identical to the old CVS 
>>>> tree.
>>>>
>>>> Feel free to start using it and let us know if you have any issues.
>>>>
>>> Any chance to have these as separate git trees instead of branches?
>
> Why? Is it just a bandwidth issue with the initial clone, or some
> other reason?
>
>>> In either case, do you expect patches against the xfs-dev or the master
>>> tree?
>
> I'll let Lachlan reply to that, but normally master I think. One thing 
> that
> is important is that any commit against the xfs-dev tree should split out
> kdb and dmapi changes into separate commits from changes to fs/xfs.
>
>>  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.
>
> yes certainly.
>
>> Specifically this page please.
>> http://xfs.org/index.php/Getting_the_latest_source_code
>
> Been waiting for the WIKI on oss to be set up - these two sites
> can simply mirror each other I guess for some or all documentation.
I suppose we could just move the xfs.org wiki to oss (once the machine 
is up/upgraded/wiki installed)
>
>> Maybe add a quick tutorial on git branches and how to create tracking
>> branches for this tree.
>
> Yes that's a good idea: git remote add ....
>
>> Also can we have something other than "unnamed repository" in the
>> description file?
>
> Yep. Niv, can you fix that up please.
>
>> xfs mailing list
>> xfs@oss.sgi.com
>> http://oss.sgi.com/mailman/listinfo/xfs
>
> Russell, would it be possible somehow for this footer to include the URL
> of the archive reference for the message containing it?
Hmm that my be difficult since the archive web stuff is generated 
periodically after that fact,
so I'm not sure if mailman has the ability build the url as part of 
sending out the email.

I'll do some googling and see if it is possible.
>
> Cheers
> -- Mark
>

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

  parent reply	other threads:[~2008-11-26  4:03 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 [this message]
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
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=492CC43D.8020704@xfs.org \
    --to=cattelan@thebarn.com \
    --cc=markgw@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