WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Accessing Lustre Code: Difference between revisions

From Obsolete Lustre Wiki
Jump to navigationJump to search
No edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<small>''(Updated: Jan 2010)''</small>
'''''NOTICE:'''''  The transition from CVS to Git took place on Monday, December 14.  For more information about the transition, see the [[Git Transition Notice]]. For details about how to migrate to Git, see [[Migrating to Git]].
'''''NOTICE:'''''  The transition from CVS to Git took place on Monday, December 14.  For more information about the transition, see the [[Git Transition Notice]]. For details about how to migrate to Git, see [[Migrating to Git]].


Line 7: Line 9:
  git clone git://git.lustre.org/prime/lustre.git  
  git clone git://git.lustre.org/prime/lustre.git  


[[new content]]<br>
'''''Note:''''' For more information about using Git, including tutorials and guides to help you get started, see the [http://git-scm.com/documentation Git documentation] page. ''For descriptions of the commands you are most likely to need, see the Commands section at the bottom of this page.''
The resulting cloned repository includes all the branches in the original repository. To see a list of the branches available in the cloned repository, enter:
 
git branch -a
 
To check out a branch or tag, use the git checkout command. For example, to check out the tag for 1.8.1.1, enter:
 
git checkout v1_8_1_1
 
For a list of commonly-used commands, along with several tutorials and guides to help you get started, see the [http://git-scm.com/documentation Git documentation]
<br>[[end new content]]
 
In order to ease initial bandwidth demands on the Git server, there will also be a torrent available of a tarball of the initial repository to allow faster downloads.  The torrent file is available [[Media:Lustre-prime-2009-12-14.tar.gz.torrent|here]] and can be downloaded and untarred, then sync'd against the Prime repository. The ''md5sum'' of that tarball is available [[Media:Lustre-prime-2009-12-14.tar.gz.md5|here]] (though torrents are already checksummed themselves and this is not necessarily required).


See [[Contribute]] for more information about developing, testing, and submitting a patch to the Lustre code.
See [[Contribute]] for more information about developing, testing, and submitting a patch to the Lustre code.
Line 35: Line 25:
Work for the next upcoming version is done on the ''master'' branch.
Work for the next upcoming version is done on the ''master'' branch.


Lustre [[Subsystem Map]] describes each of the subsystems in the Lustre code.
The Lustre [[Subsystem Map]] describes each of the subsystems in the Lustre code.

Latest revision as of 11:10, 20 January 2011

(Updated: Jan 2010)

NOTICE: The transition from CVS to Git took place on Monday, December 14. For more information about the transition, see the Git Transition Notice. For details about how to migrate to Git, see Migrating to Git.

We welcome and encourage contributions to the development and testing of a more robust, feature-rich Lustre™. You can obtain the latest bleeding-edge Lustre source code by anonymous Git access. 

git clone git://git.lustre.org/prime/lustre.git

Note: For more information about using Git, including tutorials and guides to help you get started, see the Git documentation page. For descriptions of the commands you are most likely to need, see the Commands section at the bottom of this page.

See Contribute for more information about developing, testing, and submitting a patch to the Lustre code.

Note: If you have questions or experience problems, send email to the Admins.

For more information about Git, see the Git home

Naming conventions

Stable development branches are named b{major}_{minor} (for example, b1_6 and b1_8). Even-numbered minor releases are considered stable releases. Odd-numbered minor releases correspond to alpha and beta releases and will sometimes be given v{major}_{minor}_{patch} tags to provide a point of reference for internal and external testing.

A release branch is created an official release to isolate it from further development and named b_release_{major}_{minor}_{patch} (for example, b_release_1_8_0). A final release gets a tag in the form v{major}_{minor}_{patch} (for example, v1_8_0 or v1_6_7_1).

Work for the next upcoming version is done on the master branch.

The Lustre Subsystem Map describes each of the subsystems in the Lustre code.

Retrieved from "http://wiki.old.lustre.org/index.php?title=Accessing_Lustre_Code&oldid=12276"