[ANNOUNCE] Git v2.3.1
Junio C Hamano
gitster at pobox.com
Wed Feb 25 07:02:26 GMT 2015
The latest maintenance release Git v2.3.1 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.3.1'
tag and the 'maint' branch that the tag points at:
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.3.1 Release Notes
========================
Fixes since v2.3
----------------
* The interactive "show a list and let the user choose from it"
interface "add -i" used showed and prompted to the user even when
the candidate list was empty, against which the only "choice" the
user could have made was to choose nothing.
* "git apply --whitespace=fix" used to under-allocate the memory
when the fix resulted in a longer text than the original patch.
* "git log --help" used to show rev-list options that are irrelevant
to the "log" command.
* The error message from "git commit", when a non-existing author
name was given as value to the "--author=" parameter, has been
reworded to avoid misunderstanding.
* A broken pack .idx file in the receiving repository prevented the
dumb http transport from fetching a good copy of it from the other
side.
* The documentation incorrectly said that C(opy) and R(ename) are the
only ones that can be followed by the score number in the output in
the --raw format.
* Fix a misspelled conditional that is always true.
* Code to read branch name from various files in .git/ directory
would have misbehaved if the code to write them left an empty file.
* The "git push" documentation made the "--repo=<there>" option
easily misunderstood.
* After attempting and failing a password-less authentication
(e.g. kerberos), libcURL refuses to fall back to password based
Basic authentication without a bit of help/encouragement.
* Setting diff.submodule to 'log' made "git format-patch" produce
broken patches.
* "git rerere" (invoked internally from many mergy operations) did
not correctly signal errors when told to update the working tree
files and failed to do so for whatever reason.
* "git blame HEAD -- missing" failed to correctly say "HEAD" when it
tried to say "No such path 'missing' in HEAD".
Also contains typofixes, documentation updates and trivial code clean-ups.
----------------------------------------------------------------
Changes since v2.3.0 are as follows:
Alexander Kuleshov (1):
add -i: return from list_and_choose if there is no candidate
Doug Kelly (2):
t4255: test am submodule with diff.submodule
format-patch: ignore diff.submodule setting
Jeff King (7):
git-compat-util: add xstrdup_or_null helper
builtin/apply.c: use xstrdup_or_null instead of null_strdup
builtin/commit.c: use xstrdup_or_null instead of envdup
use xstrdup_or_null to replace ternary conditionals
dumb-http: do not pass NULL path to parse_pack_index
read_and_strip_branch: fix typo'd address-of operator
do not check truth value of flex arrays
Jonathan Nieder (1):
rerere: error out on autoupdate failure
Junio C Hamano (6):
apply.c: typofix
apply: make update_pre_post_images() sanity check the given postlen
apply: count the size of postimage correctly
Documentation: what does "git log --indexed-objects" even mean?
diff-format doc: a score can follow M for rewrite
Git 2.3.1
Lukas Fleischer (1):
blame.c: fix garbled error message
Michael J Gruber (2):
commit: reword --author error message
git-push.txt: document the behavior of --repo
brian m. carlson (1):
remote-curl: fall back to Basic auth if Negotiate fails
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the git-announce
mailing list