* Bugfixes
+ - Automated merge conflict handling when changes to symbolic
+ links conflicted were completely broken. The merge-resolve
+ strategy created a regular file with conflict markers in it
+ in place of the symbolic link. The default strategy,
+ merge-recursive was even more broken. It removed the path
+ that was pointed at by the symbolic link. Both of these
+ problems have been fixed.
+
- 'git diff maint master next' did not correctly give combined
diff across three trees.
impossible to repack after accumulating many (small) packs
in the repository.
+ - 'git-diff' to review the combined diff during a conflicted
+ merge were not reading the working tree version correctly
+ when changes to a symbolic link conflicted. It should have
+ read the data using readlink(2) but read from the regular
+ file the symbolic link pointed at.
+
+ - 'git-remote' did not like period in a remote's name.
+
* Documentation updates
- added and clarified core.bare, core.legacyheaders configurations.
- updated "git-clone --depth" documentation.
-* Assorted git-gui fixes.
-
---
-exec >/var/tmp/1
-O=v1.5.0.1-35-gffa84ff
-echo O=`git describe maint`
-git shortlog --no-merges $O..maint
-
-#Local Variables:
-#mode: text
-#End:
+* Assorted git-gui fixes.
The default program to execute on the remote side when fetching. See
option \--exec of gitlink:git-fetch-pack[1].
+remote.<name>.tagopt::
+ Setting this value to --no-tags disables automatic tag following when fetching
+ from remote <name>
+
remotes.<group>::
The list of remotes which are fetched by "git remote update
<group>". See gitlink:git-remote[1].
</p>\r
</dd>\r
<dt>\r
+remote.<name>.tagopt\r
+</dt>\r
+<dd>\r
+<p>\r
+ Setting this value to --no-tags disables automatic tag following when fetching\r
+ from remote <name>\r
+</p>\r
+</dd>\r
+<dt>\r
remotes.<group>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 24-Feb-2007 11:15:45 UTC\r
+Last updated 26-Feb-2007 09:50:07 UTC\r
</div>\r
</div>\r
</body>\r
<url>. The command <tt>git fetch <name></tt> can then be used to create and\r
update remote-tracking branches <name>/<branch>.\r
</p>\r
+<p>With <tt>-f</tt> option, <tt>git fetch <name></tt> is run immediately after\r
+the remote information is set up.</p>\r
+<p>With <tt>-t <branch></tt> option, instead of the default glob\r
+refspec for the remote to track all branches under\r
+<tt>$GIT_DIR/remotes/<name>/</tt>, a refspec to track only <tt><branch></tt>\r
+is created. You can give more than one <tt>-t <branch></tt> to track\r
+multiple branche without grabbing all branches.</p>\r
+<p>With <tt>-m <master></tt> option, <tt>$GIT_DIR/remotes/<name>/HEAD</tt> is set\r
+up to point at remote's <tt><master></tt> branch instead of whatever\r
+branch the <tt>HEAD</tt> at the remote repository actually points at.</p>\r
</dd>\r
<dt>\r
<em>show</em>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Feb-2007 20:23:57 UTC\r
+Last updated 26-Feb-2007 09:50:09 UTC\r
</div>\r
</div>\r
</body>\r
Adds a remote named <name> for the repository at
<url>. The command `git fetch <name>` can then be used to create and
update remote-tracking branches <name>/<branch>.
++
+With `-f` option, `git fetch <name>` is run immediately after
+the remote information is set up.
++
+With `-t <branch>` option, instead of the default glob
+refspec for the remote to track all branches under
+`$GIT_DIR/remotes/<name>/`, a refspec to track only `<branch>`
+is created. You can give more than one `-t <branch>` to track
+multiple branche without grabbing all branches.
++
+With `-m <master>` option, `$GIT_DIR/remotes/<name>/HEAD` is set
+up to point at remote's `<master>` branch instead of whatever
+branch the `HEAD` at the remote repository actually points at.
'show'::
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 23-Feb-2007 11:13:38 UTC\r
+Last updated 26-Feb-2007 09:50:09 UTC\r
</div>\r
</div>\r
</body>\r
You are reading the documentation for the latest version of git.
Documentation for older releases are available here:
-* link:v1.5.0.1/git.html[documentation for release 1.5.0.1]
+* link:v1.5.0.2/git.html[documentation for release 1.5.0.2]
+
+* link:v1.5.0.2/RelNotes-1.5.0.2.txt[release notes for 1.5.0.2]
* link:v1.5.0.1/RelNotes-1.5.0.1.txt[release notes for 1.5.0.1]