The latest maintenance release Git v2.4.7 is now available at
the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.4.7'
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
----------------------------------------------------------------
Git v2.4.7 Release Notes
========================
Fixes since v2.4.6
------------------
* A minor regression to "git fsck" in v2.2 era was fixed; it
complained about a body-less tag object when it lacked a
separator empty line after its header to separate it with a
non-existent body.
* We used to ask libCURL to use the most secure authentication method
available when talking to an HTTP proxy only when we were told to
talk to one via configuration variables. We now ask libCURL to
always use the most secure authentication method, because the user
can tell libCURL to use an HTTP proxy via an environment variable
without using configuration variables.
* When you say "!<ENTER>" while running say "git log", you'd confuse
yourself in the resulting shell, that may look as if you took
control back to the original shell you spawned "git log" from but
that isn't what is happening. To that new shell, we leaked
GIT_PAGER_IN_USE environment variable that was meant as a local
communication between the original "Git" and subprocesses that was
spawned by it after we launched the pager, which caused many
"interesting" things to happen, e.g. "git diff | cat" still paints
its output in color by default.
Stop leaking that environment variable to the pager's half of the
fork; we only need it on "Git" side when we spawn the pager.
* Avoid possible ssize_t to int truncation.
* "git config" failed to update the configuration file when the
underlying filesystem is incapable of renaming a file that is still
open.
* A minor bugfix when pack bitmap is used with "rev-list --count".
* An ancient test framework enhancement to allow color was not
entirely correct; this makes it work even when tput needs to read
from the ~/.terminfo under the user's real HOME directory.
* Fix a small bug in our use of umask() return value.
* "git rebase" did not exit with failure when format-patch it invoked
failed for whatever reason.
* Disable "have we lost a race with competing repack?" check while
receiving a huge object transfer that runs index-pack.
Also contains typofixes, documentation updates and trivial code
clean-ups.
----------------------------------------------------------------
Changes since v2.4.6 are as follows:
Clemens Buchacher (1):
rebase: return non-zero error code if format-patch fails
Enrique Tobis (1):
http: always use any proxy auth method available
Jeff King (4):
index-pack: avoid excessive re-reading of pack directory
docs: clarify that --encoding can produce invalid sequences
rev-list: disable --use-bitmap-index when pruning commits
check_and_freshen_file: fix reversed success-check
Junio C Hamano (3):
fsck: it is OK for a tag and a commit to lack the body
pager: do not leak "GIT_PAGER_IN_USE" to the pager
Git 2.4.7
Karsten Blees (1):
config.c: fix writing config files on Windows network shares
Lawrence Siebert (1):
rev-list: add --count to usage guide
Matthieu Moy (2):
Documentation/branch: document -d --force and -m --force
Documentation/branch: document -M and -D in terms of --force
Michael Haggerty (1):
strbuf: strbuf_read_file() should return ssize_t
Richard Hansen (2):
Revert "test-lib.sh: do tests for color support after changing HOME"
test-lib.sh: fix color support when tput needs ~/.terminfo
Torsten Bögershausen (1):
git-checkout.txt: document "git checkout <pathspec>" better
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
