The latest maintenance release Git v1.9.2 is now available at
the usual places.
The release tarballs are found at:
The following public repositories all have a copy of the v1.9.2
tag and the maint branch that the tag points at:
url = https://kernel.googlesource.com/pub/scm/git/git
url = git://repo.or.cz/alt-git.git
url = https://code.google.com/p/git-core/
url = git://git.sourceforge.jp/gitroot/git-core/git.git
url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core
url = https://github.com/gitster/git
The http://code.google.com/p/git-core/downloads/ site no longer
accepts new tarballs for download; while the older release tarballs
are still there, this one (and future ones) will not be.
Git v1.9.2 Release Notes
Fixes since v1.9.1
* Documentation and in-code comments had many instances of mistaken
use of "nor", which have been corrected.
* "git fetch --prune", when the right-hand-side of multiple fetch
refspecs overlap (e.g. storing "refs/heads/*" to
"refs/remotes/origin/*", while storing "refs/frotz/*" to
"refs/remotes/origin/fr/*"), aggressively thought that lack of
"refs/heads/fr/otz" on the origin site meant we should remove
"refs/remotes/origin/fr/otz" from us, without checking their
Note that such a configuration is inherently unsafe (think what
should happen when "refs/heads/fr/otz" does appear on the origin
site), but that is not a reason not to be extra careful.
* "git update-ref --stdin" did not fail a request to create a ref
when the ref already existed.
* "git diff --no-index -Mq a b" fell into an infinite loop.
* When it is not necessary to edit a commit log message (e.g. "git
commit -m" is given a message without specifying "-e"), we used to
disable the spawning of the editor by overriding GIT_EDITOR, but
this means all the uses of the editor, other than to edit the
commit log message, are also affected.
* "git status --porcelain --branch" showed its output with labels
"ahead/behind/gone" translated to the user's locale.
* "git mv" that moves a submodule forgot to adjust the array that
uses to keep track of which submodules were to be moved to update
* Length limit for the pathname used when removing a path in a deep
subdirectory has been removed to avoid buffer overflows.
* The test helper lib-terminal always run an actual test_expect_*
when included, which screwed up with the use of skil-all that may
have to be done later.
* "git index-pack" used a wrong variable to name the keep-file in an
error message when the file cannot be written or closed.
* "rebase -i" produced a broken insn sheet when the title of a commit
happened to contain '\n' (or ended with '\c') due to a careless use
* There were a few instances of 'git-foo' remaining in the
documentation that should have been spelled 'git foo'.
* Serving objects from a shallow repository needs to write a
new file to hold the temporary shallow boundaries but it was not
cleaned when we exit due to die() or a signal.
* When "git stash pop" stops after failing to apply the stash
(e.g. due to conflicting changes), the stash is not dropped. State
that explicitly in the output to let the users know.
* The labels in "git status" output that describe the nature of
conflicts (e.g. "both deleted") were limited to 20 bytes, which was
too short for some l10n (e.g. fr).
Changes since v1.9.1 are as follows:
Aman Gupta (1):
update-ref: fail create operation over stdin if ref already exists
Benoit Pierre (7):
merge hook tests: fix missing '&&' in test
merge hook tests: use 'test_must_fail' instead of '!'
test patch hunk editing with "commit -p -m"
commit: fix patch hunk editing with "commit -p -m"
merge: fix GIT_EDITOR override for commit hook
merge hook tests: fix and update tests
run-command: mark run_hook_with_custom_index as deprecated
Carlos Martín Nieto (2):
fetch: add a failing test for prunning with overlapping refspecs
fetch: handle overlaping refspecs on --prune
Jeff King (6):
shallow: use stat_validity to check for up-to-date file
shallow: automatically clean up shallow tempfiles
t/lib-terminal: make TTY a lazy prerequisite
shallow: verify shallow file after taking lock
date: recognize bogus FreeBSD gmtime output
t4212: loosen far-in-future test for AIX
John Keeping (1):
builtin/mv: fix out of bounds write
Jonathan Nieder (2):
wt-status: extract the code to compute width for labels
wt-status: i18n of section labels
Junio C Hamano (8):
stash pop: mention we did not drop the stash upon failing to apply
wt-status: make full label string to be subject to l10n
wt-status: lift the artificual "at least 20 columns" floor
index-pack: report error using the correct variable
diff-no-index: correctly diagnose error return from diff_opt_parse()
Start preparing for 1.9.1
Update draft release notes to 1.9.2
Justin Lebar (4):
Documentation: fix misuses of "nor"
contrib: fix misuses of "nor"
comments: fix misuses of "nor"
code and test: fix misuses of "nor"
Matthieu Moy (1):
status: disable translation when --porcelain is used
Michael Haggerty (2):
checkout_entry(): use the strbuf throughout the function
entry.c: fix possible buffer overflow in remove_subtree()
Ramkumar Ramachandra (1):
Documentation/merge-strategies: avoid hyphenated commands
Thomas Ackermann (1):
doc/http-backend: missing accent grave in literal mark-up
Uwe Storbeck (2):
rebase -i: do not "echo" random user-supplied strings
test-lib.sh: do not "echo" caller-supplied strings
brian m. carlson (1):
mv: prevent mismatched data when ignoring errors.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html