--- /dev/null
+GIT v1.6.0.2 Release Notes
+==========================
+
+Fixes since v1.6.0.1
+--------------------
+
+* Installation on platforms that needs .exe suffix to git-* programs were
+ broken in 1.6.0.1.
+
+* Installation on filesystems without symbolic links support did nto
+ work well.
+
+* In-tree documentations and test scripts now use "git foo" form to set a
+ better example, instead of the "git-foo" form (which is an acceptable
+ form if you have "PATH=$(git --exec-path):$PATH" in your script)
+
+* Many commands did not use the correct working tree location when used
+ with GIT_WORK_TREE environment settings.
+
+
+
+* "git apply --unidiff-zero" incorrectly applied a -U0 patch that inserts
+ a new line before the second line.
+
+* "git clone $there $here/" with extra trailing slashes after explicit
+ local directory name $here did not work as expected.
+
+* "git diff --dirstat -M" did not add changes in subdirectories up
+ correctly for renamed paths.
+
+* "git for-each-ref refs/heads/" did not work as expected.
+
+* "git log --grep=pattern -i" did not ignore case.
+
+* "git log --pretty="%ad" --date=short" did not use short format when
+ showing the timestamp.
+
+* Build procedure for "git shell" that used stub versions of some
+ functions and globals was not understood by linkers on some platforms.
+
+* "git verify-pack -v" did not work correctly when given more than one
+ packfile.
+
+Also contains many documentation updates.
+
+--
+exec >/var/tmp/1
+O=v1.6.0.1-49-g6a42cfe
+echo O=$(git describe maint)
+git shortlog --no-merges $O..maint
* The underlying diff machinery to produce textual output has been
optimized, which would result in faster "git blame" processing.
+* Most of the test scripts (but not the ones that try to run servers)
+ can be run in parallel.
+
(usability, bells and whistles)
* "git checkout --track origin/hack" used to be a syntax error. It now
DWIMs to create a corresponding local branch "hack", i.e. acts as if you
said "git checkout --track -b hack origin/hack".
+* "git cherry-pick" can also utilize rerere for conflict resolution.
+
+* "git commit --author=$name" can look up author name from existing
+ commits.
+
+* "git count-objects" reports the on-disk footprint for packfiles and
+ their corresponding idx files.
+
+* "git daemon" learned --max-connections=<count> option.
+
* "git diff" learned to mimick --suppress-blank-empty from GNU diff via a
configuration option.
+* "git diff" learned to put more sensible hunk headers for Python and
+ HTML contents.
+
+* "git help" learned to use GIT_MAN_VIEWER environment variable before
+ using "man" program.
+
* "git imap-send" can optionally talk SSL.
+* "git index-pack" is more careful against disk corruption while
+ completing a thin pack.
+
+* "git log --check" and "git log --exit-code" passes their underlying diff
+ status with their exit status code.
+
+* "git log" learned --simplify-merges, a milder variant of --full-history;
+ "gitk --simplify-merges" is easier to view than with --full-history.
+
+* "git merge --squash" and "git merge --no-ff" into an unborn branch are
+ noticed as user errors.
+
+* "git merge -s $strategy" can use a custom built strategy if you have a
+ command "git-merge-$strategy" on your $PATH.
+
+* "git reflog expire branch" can be used in place of "git reflog expire
+ refs/heads/branch".
+
+* "git submodule foreach" subcommand allows you to iterate over checked
+ out submodules.
+
+* "git submodule sync" subcommands allows you to update the origin URL
+ recorded in submodule directories from the toplevel .gitmodules file.
+
(internal)
* "git hash-object" learned to lie about the path being hashed, so that
All of the fixes in v1.6.0.X maintenance series are included in this
release, unless otherwise noted.
+* "git add" and "git update-index" incorrectly allowed adding S/F when S
+ is a tracked symlink that points at a directory D that has a path F in
+ it (we still need to fix a similar nonsense when S is a submodule and F
+ is a path in it).
+
+* "git diff --stdin" used to take two trees on a line and compared them,
+ but we droppped support for such a use case long time ago. This has
+ been resurrected.
+
+* "git filter-branch" failed to rewrite a tag name with slashes in it.
+
+* "git push --tags --all $there" failed with generic usage message without
+ telling saying these two options are incompatible.
+
--
exec >/var/tmp/1
-O=v1.6.0-48-ge28a867
+O=v1.6.0.1-215-g9b8ae93
echo O=$(git describe master)
git shortlog --no-merges $O..master ^maint
</dt>\r
<dd>\r
<p>\r
- The password(5) gecos field is longer than a giant static buffer.\r
+ The passwd(5) gecos field is longer than a giant static buffer.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- The password(5) name field is longer than a giant static buffer.\r
+ The passwd(5) name field is longer than a giant static buffer.\r
</p>\r
</dd>\r
</dl></div>\r
<div class="olist"><ol>\r
<li>\r
<p>\r
-<em>git-commit-tree</em> (hence, <em>git-commit</em> which uses it) issues\r
+<em>git-commit</em> and <em>git-commit-tree</em> issues\r
a warning if the commit log message given to it does not look\r
like a valid UTF-8 string, unless you explicitly say your\r
project uses a legacy encoding. The way to say this is to\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-08-10 03:55:18 UTC\r
+Last updated 2008-09-04 00:23:35 UTC\r
</div>\r
</div>\r
</body>\r
You don't exist. Go away!::
The passwd(5) gecos field couldn't be read
Your parents must have hated you!::
- The password(5) gecos field is longer than a giant static buffer.
+ The passwd(5) gecos field is longer than a giant static buffer.
Your sysadmin must hate you!::
- The password(5) name field is longer than a giant static buffer.
+ The passwd(5) name field is longer than a giant static buffer.
Discussion
----------
<div class="olist"><ol>\r
<li>\r
<p>\r
-<em>git-commit-tree</em> (hence, <em>git-commit</em> which uses it) issues\r
+<em>git-commit</em> and <em>git-commit-tree</em> issues\r
a warning if the commit log message given to it does not look\r
like a valid UTF-8 string, unless you explicitly say your\r
project uses a legacy encoding. The way to say this is to\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-09-03 05:19:53 UTC\r
+Last updated 2008-09-04 00:23:35 UTC\r
</div>\r
</div>\r
</body>\r
<div class="olist"><ol>\r
<li>\r
<p>\r
-<em>git-commit-tree</em> (hence, <em>git-commit</em> which uses it) issues\r
+<em>git-commit</em> and <em>git-commit-tree</em> issues\r
a warning if the commit log message given to it does not look\r
like a valid UTF-8 string, unless you explicitly say your\r
project uses a legacy encoding. The way to say this is to\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-09-03 05:19:58 UTC\r
+Last updated 2008-09-04 00:23:36 UTC\r
</div>\r
</div>\r
</body>\r
<div class="olist"><ol>\r
<li>\r
<p>\r
-<em>git-commit-tree</em> (hence, <em>git-commit</em> which uses it) issues\r
+<em>git-commit</em> and <em>git-commit-tree</em> issues\r
a warning if the commit log message given to it does not look\r
like a valid UTF-8 string, unless you explicitly say your\r
project uses a legacy encoding. The way to say this is to\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-08-29 08:56:30 UTC\r
+Last updated 2008-09-04 00:23:36 UTC\r
</div>\r
</div>\r
</body>\r
Cause the logical variables to be listed. In addition, all the\r
variables of the git configuration file .git/config are listed\r
as well. (However, the configuration variables listing functionality\r
- is deprecated in favor of <em>git-config -l</em>.)\r
+ is deprecated in favor of <em>git config -l</em>.)\r
</p>\r
</dd>\r
</dl></div>\r
</dt>\r
<dd>\r
<p>\r
- The password(5) gecos field is longer than a giant static buffer.\r
+ The passwd(5) gecos field is longer than a giant static buffer.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- The password(5) name field is longer than a giant static buffer.\r
+ The passwd(5) name field is longer than a giant static buffer.\r
</p>\r
</dd>\r
</dl></div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-07-06 05:17:07 UTC\r
+Last updated 2008-09-04 00:23:37 UTC\r
</div>\r
</div>\r
</body>\r
Cause the logical variables to be listed. In addition, all the
variables of the git configuration file .git/config are listed
as well. (However, the configuration variables listing functionality
- is deprecated in favor of 'git-config -l'.)
+ is deprecated in favor of 'git config -l'.)
EXAMPLE
--------
You don't exist. Go away!::
The passwd(5) gecos field couldn't be read
Your parents must have hated you!::
- The password(5) gecos field is longer than a giant static buffer.
+ The passwd(5) gecos field is longer than a giant static buffer.
Your sysadmin must hate you!::
- The password(5) name field is longer than a giant static buffer.
+ The passwd(5) name field is longer than a giant static buffer.
SEE ALSO
--------
does not forbid it. However, there are a few things to keep in
mind.
-. 'git-commit-tree' (hence, 'git-commit' which uses it) issues
+. 'git-commit' and 'git-commit-tree' issues
a warning if the commit log message given to it does not look
like a valid UTF-8 string, unless you explicitly say your
project uses a legacy encoding. The way to say this is to
projects / git.git / commitdiff