From: Russell Cattelan <cattelan@thebarn.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: xfs-cmds git tree re-imported
Date: Mon, 29 Dec 2008 17:04:24 -0600 [thread overview]
Message-ID: <49595778.6000200@thebarn.com> (raw)
Based on Christoph's work to the xfs-authors list and his fix to cvsps
that can now accurately detect ptools changes sets the xfs-cmds tree
has been re-imported to git.
Please see for more info on the git trees in general.
http://xfs.org/index.php/Getting_the_latest_source_code
Note a new clone of the xfs-cmds tree is required since this is a fresh
import
and does not share any commit data with the old import of xfs-cmds.
The xfs-import and dmapi-import trees have also been re-imported.
These trees are not build able trees but are good reference sources as
they have much of the xfs history.
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=cattelan/xfs-import/.git;a=summary
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=cattelan/dmapi-import/.git;a=summary
-Russell
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2008-12-29 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 23:04 Russell Cattelan [this message]
2008-12-30 17:46 ` xfs-cmds git tree re-imported Josef 'Jeff' Sipek
2008-12-30 17:55 ` 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=49595778.6000200@thebarn.com \
--to=cattelan@thebarn.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