Whamcloud - gitweb
LU-9019 lfsck: migrate to 64 bit time
[fs/lustre-release.git] / README
diff --git a/README b/README
index 8f274ba..f1118fb 100644 (file)
--- a/README
+++ b/README
@@ -1,13 +1,23 @@
-Instructions for building, configuring and running Lustre can be found at:
-    http://wiki.whamcloud.com/display/PUB/Submitting+Changes
-and:
-    http://wiki.whamcloud.com/display/PUB/Using+Gerrit
+Instructions for building, configuring and running Lustre:
+    https://wiki.hpdd.intel.com/display/PUB/Building+Lustre+from+Source
+and
+    https://wiki.hpdd.intel.com/display/PUB/Getting+started+with+Lustre.
+
+Instructions for contributing patches for Lustre:
+    https://wiki.hpdd.intel.com/display/PUB/Submitting+Changes
+and
+    https://wiki.hpdd.intel.com/display/PUB/Using+Gerrit
 
 The Lustre Coding Style Guidelines can be found at:
 
 The Lustre Coding Style Guidelines can be found at:
-    http://wiki.whamcloud.com/display/PUB/Coding+Guidelines
+    https://wiki.hpdd.intel.com/display/PUB/Coding+Guidelines
+
+The Lustre Test Script Style Guidelines can be found at:
+    https://wiki.hpdd.intel.com/display/PUB/Test+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:
 
 
 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:
 
-    cp build/{prepare-,}commit-msg .git/hooks/
+    cd .git/hooks
+    ln -s ../../contrib/git-hooks/{prepare-,}commit-msg ./
+    cd ../..