Difference between revisions of "Getting the latest source code"

From xfs.org
Jump to navigation Jump to search
m (fix whitespace in git example)
Line 1: Line 1:
= <font face="ARIAL NARROW,HELVETICA"> XFS: Source Code </font> =
 
  
There are several ways to access the current XFS code.
+
== <font face="ARIAL NARROW,HELVETICA"> Using GIT trees </font> ==
 
 
* '''Mainline kernels'''<br /> XFS has been maintained in the official Linux kernel [http://www.kernel.org/ kernel trees] starting with Linux 2.4 and is frequently updated with the latest stable fixes and features from the SGI XFS development team.
 
 
 
* '''Vendor kernels'''<br /> All modern Linux distributions include support for XFS. SGI actively works with [http://www.suse.com/  SUSE] to provide a supported version of XFS in that distribution.
 
 
 
* '''XFS userspace'''<br /> Sgi also provides [ftp://oss.sgi.com/projects/xfs source code taballs] of the xfs userspace tools. These tarballs form the basis of the xfsprogs packages found in Linux distributions.
 
 
 
* '''CVS web'''<br /> Browse the XFS source trees.
 
** [http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/ 2.6.x-xfs]
 
** [http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/ xfs-cmds]
 
 
 
* '''CVS trees'''<br /> Direct CVS access to the most recent XFS changes. See below.
 
 
 
== <font face="ARIAL NARROW,HELVETICA"> Using CVS trees </font> ==
 
 
 
The cvs trees are automated mirrors of the SGI internal ptools manage source trees.
 
 
 
[http://www.cvshome.org/new_users.html CVS for new users] contains links to general CVS documentation.
 
 
 
Set the CVSROOT environment variable.
 
  
{| width="100%" cellspacing="2"
+
[[XFS git howto]]
| bgcolor="#DFDFDF" | <br /><tt>$ export CVSROOT=':pserver:cvs@oss.sgi.com:/cvs'</tt><br /><tt>''(for sh, bash, ksh, or similar shells)''</tt><br /><tt>$ setenv CVSROOT :pserver:cvs@oss.sgi.com:/cvs</tt><br /><tt>''(for csh or tcsh shells)''</tt><br />
 
|}
 
 
 
Login to the CVS server (this only needs to be done ONCE, not every time you access CVS).
 
 
 
{| width="100%" cellspacing="2"
 
| bgcolor="#DFDFDF" | <br /><tt>$ cvs login</tt><br />''(the password is "''cvs''")''<br />
 
|}
 
 
 
Now grab the XFS source tree(s) of interest:
 
 
 
{| width="100%" cellspacing="2"
 
| bgcolor="#DFDFDF" | <br /><tt>$ cvs checkout linux-2.6-xfs</tt><br /><tt>$ cvs checkout xfs-cmds</tt><br />
 
|}
 
 
 
Subsequently, you can checkout new code using:
 
 
 
{| width="100%" cellspacing="2"
 
| bgcolor="#DFDFDF" | <br /><tt>$ cvs update -d</tt><br />
 
|}
 
 
 
== <font face="ARIAL NARROW,HELVETICA"> Using GIT trees </font> ==
 
  
 
The Git trees are automated mirrored copied of the cvs trees using git-cvsimport.
 
The Git trees are automated mirrored copied of the cvs trees using git-cvsimport.
Line 64: Line 21:
 
<tt>$ git clone git://oss.sgi.com/xfs/xfs-2.6</tt><br />
 
<tt>$ git clone git://oss.sgi.com/xfs/xfs-2.6</tt><br />
 
|}
 
|}
 +
 +
 +
== <font face="ARIAL NARROW,HELVETICA">XFS cvs trees </font>
 +
 +
The cvs trees were created using a script that converted sgi's internal
 +
ptools repository to a cvs repository, so the cvs trees were considered read only.
 +
 +
At this point a new development is being managed by the git trees so the cvs trees
 +
are not longer active in terms of current development and should only be used
 +
for reference.
 +
 +
[[XFS CVS howto]]

Revision as of 17:29, 8 January 2009

Using GIT trees

XFS git howto

The Git trees are automated mirrored copied of the cvs trees using git-cvsimport. Since git-cvsimport utilized the tool cvsps to recreate the atomic commits of ptools or "mod" it is easier to see the entire change that was committed using git.

git-cvsimport generated trees.

Changes headed for the main linux 2.6 tree, manual merges.

Cloning the git trees for local use:


$ git clone git://oss.sgi.com/linux-2.6-xfs-from-cvs
$ git clone git://oss.sgi.com/xfs-cmds
$ git clone git://oss.sgi.com/xfs/xfs-2.6


== XFS cvs trees

The cvs trees were created using a script that converted sgi's internal ptools repository to a cvs repository, so the cvs trees were considered read only.

At this point a new development is being managed by the git trees so the cvs trees are not longer active in terms of current development and should only be used for reference.

XFS CVS howto