-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
- Loading branch information
Junio C Hamano
committed
Sep 10, 2012
1 parent
f56d036
commit 23193cf
Showing
2 changed files
with
63 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
Git 1.7.12.1 Release Notes | ||
========================== | ||
|
||
Fixes since v1.7.12 | ||
------------------- | ||
|
||
* "ciabot" script (in contrib/) has been updated with extensive | ||
documentation. | ||
|
||
* The "--rebase" option to "git pull" can be abbreviated to "-r", | ||
but we didn't document it. | ||
|
||
* It was generally understood that "--long-option"s to many of our | ||
subcommands can be abbreviated to the unique prefix, but it was not | ||
easy to find it described for new readers of the documentation set. | ||
|
||
* The "--topo-order", "--date-order" (and the lack of either means | ||
the default order) options to "rev-list" and "log" family of | ||
commands were poorly described in the documentation. | ||
|
||
* Older parts of the documentation described as if having a regular | ||
file in .git/refs/ hierarchy were the only way to have branches and | ||
tags, which is not true for quite some time. | ||
|
||
* A utility shell function test_seq has been added as a replacement | ||
for the 'seq' utility found on some platforms. | ||
|
||
* Fallback 'getpass' implementation made unportable use of stdio API. | ||
|
||
* "git commit --amend" let the user edit the log message and then | ||
died when the human-readable committer name was given | ||
insufficiently by getpwent(3). | ||
|
||
* "git prune" without "-v" used to warn about leftover temporary | ||
files (which is an indication of an earlier aborted operation). | ||
|
||
* The reflog entries left by "git rebase" and "git rebase -i" were | ||
inconsistent (the interactive one gave an abbreviated object name). | ||
|
||
* When the user exports a non-default IFS without HT, scripts that | ||
rely on being able to parse "ls-files -s | while read a b c..." | ||
started to fail. Protect them from such a misconfiguration. | ||
|
||
* When "git push" triggered the automatic gc on the receiving end, a | ||
message from "git prune" that said it was removing cruft leaked to | ||
the standard output, breaking the communication protocol. | ||
|
||
* "git diff" had a confusion between taking data from a path in the | ||
working tree and taking data from an object that happens to have | ||
name 0{40} recorded in a tree. | ||
|
||
* "git send-email" did not unquote encoded words that appear on the | ||
header correctly, and lost "_" from strings. | ||
|
||
* When the user gives an argument that can be taken as both a | ||
revision name and a pathname without disambiguating with "--", we | ||
used to give a help message "Use '--' to separate". The message | ||
has been clarified to show where that '--' goes on the command | ||
line. | ||
|
||
* "gitweb" when used with PATH_INFO failed to notice directories with | ||
SP (and other characters that need URL-style quoting) in them. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
Documentation/RelNotes/1.7.12.txt | ||
Documentation/RelNotes/1.7.12.1.txt |