.git/objects/info/alternates to share the objects\r
with the source repository. The resulting repository\r
starts out without any object of its own.\r
- <strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use\r
- it unless you understand what it does. If you clone your\r
- repository using this option, then delete branches in the\r
- source repository and then run <a href="git-gc.html">git-gc(1)</a> using the\r
- <em>--prune</em> option in the source repository, it may remove\r
- objects which are referenced by the cloned repository.\r
</p>\r
+<p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use\r
+it unless you understand what it does. If you clone your\r
+repository using this option, then delete branches in the\r
+source repository and then run <a href="git-gc.html">git-gc(1)</a> using the\r
+<em>--prune</em> option in the source repository, it may remove\r
+objects which are referenced by the cloned repository.</p>\r
</dd>\r
<dt>\r
--reference <repository>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 24-Jan-2008 07:28:35 UTC\r
+Last updated 14-Feb-2008 00:51:07 UTC\r
</div>\r
</div>\r
</body>\r
.git/objects/info/alternates to share the objects
with the source repository. The resulting repository
starts out without any object of its own.
- *NOTE*: this is a possibly dangerous operation; do *not* use
- it unless you understand what it does. If you clone your
- repository using this option, then delete branches in the
- source repository and then run linkgit:git-gc[1] using the
- '--prune' option in the source repository, it may remove
- objects which are referenced by the cloned repository.
++
+*NOTE*: this is a possibly dangerous operation; do *not* use
+it unless you understand what it does. If you clone your
+repository using this option, then delete branches in the
+source repository and then run linkgit:git-gc[1] using the
+'--prune' option in the source repository, it may remove
+objects which are referenced by the cloned repository.
<dd>\r
<p>\r
Attempt to detect merges based on the commit message with a custom\r
- regex. It can be used with <em>-m</em> to also see the default regexes.\r
- You must escape forward slashes.\r
+ regex. It can be used with <em>-m</em> to enable the default regexes\r
+ as well. You must escape forward slashes.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:10 UTC\r
+Last updated 14-Feb-2008 00:51:07 UTC\r
</div>\r
</div>\r
</body>\r
-M <regex>::
Attempt to detect merges based on the commit message with a custom
- regex. It can be used with '-m' to also see the default regexes.
- You must escape forward slashes.
+ regex. It can be used with '-m' to enable the default regexes
+ as well. You must escape forward slashes.
-S <regex>::
Skip paths matching the regex.
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 02-Feb-2008 06:48:21 UTC\r
+Last updated 14-Feb-2008 00:51:08 UTC\r
</div>\r
</div>\r
</body>\r
branch of the `git.git` repository.
Documentation for older releases are available here:
-* link:v1.5.4/git.html[documentation for release 1.5.4]
+* link:v1.5.4.1/git.html[documentation for release 1.5.4.1]
* release notes for
+ link:RelNotes-1.5.4.1.txt[1.5.4.1],
link:RelNotes-1.5.4.txt[1.5.4].
* link:v1.5.3.8/git.html[documentation for release 1.5.3.8]