forked from lustre/lustre-release
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
33 lines (26 loc) · 1.29 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
Many resources for using, configuring, and troubleshooting Lustre are at:
http://wiki.lustre.org/
The low-volume list for announcements of new releases is at:
http://lists.lustre.org/listinfo.cgi/lustre-announce-lustre.org
The generic Lustre discussion mailing list is available at:
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
The Lustre developer mailing list is at:
http://lists.lustre.org/pipermail/lustre-devel-lustre.org
Instructions for building, configuring and running Lustre:
http://wiki.lustre.org/Compiling_Lustre
and
https://wiki.whamcloud.com/display/PUB/Getting+started+with+Lustre.
Instructions for contributing patches for Lustre:
http://wiki.lustre.org/Submitting_Changes
and
http://wiki.lustre.org/Using_Gerrit
The Lustre Coding Style Guidelines can be found at:
http://wiki.lustre.org/Lustre_Coding_Style_Guidelines
The Lustre Test Script Style Guidelines can be found at:
http://wiki.lustre.org/Lustre_Script_Coding_Style
In order to improve the quality of patches submitted to the Lustre tree,
it is possible to automatically check every patch and commit against the
Lustre Coding Guidelines. To do this, run in the top-level lustre/ tree:
cd .git/hooks
ln -s ../../contrib/git-hooks/{prepare-,}commit-msg ./
cd ../..