From: Russell Cattelan <cattelan@thebarn.com>
To: Lachlan McIlroy <lachlan@sgi.com>, xfs@oss.sgi.com
Subject: Re: New XFS git tree on oss.sgi.com
Date: Tue, 25 Nov 2008 08:27:09 -0600 [thread overview]
Message-ID: <492C0B3D.3040002@thebarn.com> (raw)
In-Reply-To: <20081125081644.GA20644@infradead.org>
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?
>
> 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.
>
>
Specifically this page please.
http://xfs.org/index.php/Getting_the_latest_source_code
Maybe add a quick tutorial on git branches and how to create tracking
branches for this tree.
Also can we have something other than "unnamed repository" in the
description file?
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-11-25 15: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 [this message]
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
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=492C0B3D.3040002@thebarn.com \
--to=cattelan@thebarn.com \
--cc=lachlan@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