-GIT v1.5.1.3 Release Notes (draft)
+GIT v1.5.1.3 Release Notes
==========================
Fixes since v1.5.1.2
- git-svn inconsistently stripped away username from the URL
only when svnsync_props was in use.
+ - git-svn got confused when handling symlinks on Mac OS.
+
- git-send-email was not quoting recipient names that have
period '.' in them. Also it did not allow overriding
envelope sender, which made it impossible to send patches to
packfiles incorrectly closed the fd that was still being
used to read the pack.
----
-exec >/var/tmp/1
-O=v1.5.1.2-23-gbf7af11
-echo O=`git describe refs/heads/maint`
-git shortlog --no-merges $O..refs/heads/maint
+ - import-tars contributed front-end for fastimport was passing
+ wrong directory modes without checking.
+
+ - git-fastimport trusted its input too much and allowed to
+ create corrupt tree objects with entries without a name.
+
+ - git-fetch needlessly barfed when too long reflog action
+ description was given by the caller.
+
+Also contains various documentation updates.
+
considered a binary or text (the former would be treated by
'git diff' not to produce textual output; the latter can go
through the line endings conversion process in repositories
- with core.autocrlf set), and specify a custom 3-way merge
- driver.
+ with core.autocrlf set), expand and unexpand '$ident$' keyword
+ with blob object name, specify a custom 3-way merge driver,
+ and specify a custom diff driver. You can also apply
+ arbitrary filter to contents on check-in/check-out codepath
+ but this feature is an extremely sharp-edged razor and needs
+ to be handled with caution (do not use it unless you
+ understand the earlier mailing list discussion on keyward
+ expansion).
* The packfile format now optionally suports 64-bit index.
commit -a" (i.e. update the index to match the working
tree); it obviously does not make a commit.
+ - "git clean" honors a new configuration, "clean.requireforce". When
+ set to true, this makes "git clean" a no-op, preventing you
+ from losing files by typing "git clean" when you meant to
+ say "make clean". You can still say "git clean -f" to
+ override this.
+
+ - "git log" family of commands learned --date={local,relative,default}
+ option. --date=relative is synonym to the --relative-date.
+ --date=local gives the timestamp in local timezone.
+
* Updated behavior of existing commands.
+ - When $GIT_COMMITTER_EMAIL or $GIT_AUTHOR_EMAIL is not set
+ but $EMAIL is set, the latter is used as a substitute.
+
- "git diff --stat" shows size of preimage and postimage blobs
for binary contents. Earlier it only said "Bin".
- "gitview" (in contrib/ section) learned to better support
"git-annotate".
+ - "git diff $commit1:$path2 $commit2:$path2" can now report
+ mode changes between the two blobs.
+
- Local "git fetch" from a repository whose object store is
one of the alternates (e.g. fetching from the origin in a
repository created with "git clone -l -s") avoids
downloading objects unnecessary.
+ - "git blame" uses .mailmap to canonicalize the author name
+ just like "git shortlog" does.
+
* Builds
- git-p4import has never been installed; now there is an
* Performance Tweaks
- - optimized "git-rev-list --bisect" (hence "git-bisect").
+ - Optimized "git-rev-list --bisect" (hence "git-bisect").
- - optimized "git-add $path" in a large directory, most of
+ - Optimized "git-add $path" in a large directory, most of
whose contents are ignored.
+ - The recursive merge strategy updated a worktree file that
+ was changed identically in two branches, when one of them
+ renamed it. We do not do that when there is no rename, so
+ match that behaviour.
Fixes since v1.5.1
------------------
will not be backported to 1.5.1.x series, as it is rather an
intrusive change.
+ - git-fetch had trouble with a remote with insanely large number
+ of refs.
+
* Documentation updates
* Performance Tweaks
--
exec >/var/tmp/1
-O=v1.5.1.2-242-g2d76548
+O=v1.5.2-rc0-106-g07c785d
echo O=`git describe refs/heads/master`
git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint
</dt>\r
<dd>\r
<p>\r
- If set, specifies the outgoing SMTP server to use. A full\r
- pathname of a sendmail-like program can be specified instead;\r
+ If set, specifies the outgoing SMTP server to use (e.g.\r
+ <tt>smtp.example.com</tt> or a raw IP address). Alternatively it can\r
+ specify a full pathname of a sendmail-like program instead;\r
the program must support the <tt>-i</tt> option. Default value can\r
be specified by the <em>sendemail.smtpserver</em> configuration\r
option; the built-in default is <tt>/usr/sbin/sendmail</tt> or\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Apr-2007 07:19:26 UTC\r
+Last updated 01-May-2007 03:05:35 UTC\r
</div>\r
</div>\r
</body>\r
--in-reply-to::
Specify the contents of the first In-Reply-To header.
- Subsequent emails will refer to the previous email
+ Subsequent emails will refer to the previous email
instead of this if --chain-reply-to is set (the default)
Only necessary if --compose is also set. If --compose
is not set, this will be prompted for.
all that is output.
--smtp-server::
- If set, specifies the outgoing SMTP server to use. A full
- pathname of a sendmail-like program can be specified instead;
+ If set, specifies the outgoing SMTP server to use (e.g.
+ `smtp.example.com` or a raw IP address). Alternatively it can
+ specify a full pathname of a sendmail-like program instead;
the program must support the `-i` option. Default value can
be specified by the 'sendemail.smtpserver' configuration
option; the built-in default is `/usr/sbin/sendmail` or
<dd>\r
<p>\r
When given an SVN revision number of the form <em>rN</em>, returns the\r
- corresponding git commit hash. When given a tree-ish, returns the\r
- corresponding SVN revision number.\r
+ corresponding git commit hash (this can optionally be followed by a\r
+ tree-ish to specify which branch should be searched). When given a\r
+ tree-ish, returns the corresponding SVN revision number.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 29-Apr-2007 18:29:51 UTC\r
+Last updated 01-May-2007 03:05:35 UTC\r
</div>\r
</div>\r
</body>\r
--
'find-rev'::
When given an SVN revision number of the form 'rN', returns the
- corresponding git commit hash. When given a tree-ish, returns the
- corresponding SVN revision number.
+ corresponding git commit hash (this can optionally be followed by a
+ tree-ish to specify which branch should be searched). When given a
+ tree-ish, returns the corresponding SVN revision number.
'set-tree'::
You should consider using 'dcommit' instead of this command.
in a coherent way to git enlightenment ;-).</p>\r
<p>The COMMAND is either a name of a Git command (see below) or an alias\r
as defined in the configuration file (see <a href="git-config.html">git-config(1)</a>).</p>\r
+<p>Formatted and hyperlinked version of the latest git\r
+documentation can be viewed at\r
+<tt>http://www.kernel.org/pub/software/scm/git/docs/</tt>.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 29-Apr-2007 18:29:52 UTC\r
+Last updated 01-May-2007 03:05:35 UTC\r
</div>\r
</div>\r
</body>\r
The COMMAND is either a name of a Git command (see below) or an alias
as defined in the configuration file (see gitlink:git-config[1]).
+Formatted and hyperlinked version of the latest git
+documentation can be viewed at
+`http://www.kernel.org/pub/software/scm/git/docs/`.
+
ifdef::stalenotes[]
[NOTE]
============
projects / git.git / commitdiff