[thirdparty/git.git] / Documentation / RelNotes / 1.6.4.1.txt

GIT v1.6.4.1 Release Notes
==========================

Fixes since v1.6.4
------------------

 * An unquoted value in the configuration file, when it contains more than
   one whitespaces in a row, got them replaced with a single space.

 * "git am" used to accept a single piece of e-mail per file (not a mbox)
   as its input, but multiple input format support in v1.6.4 broke it.
   Apparently many people have been depending on this feature.

 * The short help text for "git filter-branch" command was a single long
   line, wrapped by terminals, and was hard to read.

 * The "recursive" strategy of "git merge" segfaulted when a merge has
   more than one merge-bases, and merging of these merge-bases involves
   a rename/rename or a rename/add conflict.

 * "git pull --rebase" did not use the right fork point when the
   repository has already fetched from the upstream that rewinds the
   branch it is based on in an earlier fetch.

 * Explain the concept of fast-forward more fully in "git push"
   documentation, and hint to refer to it from an error message when the
   command refuses an update to protect the user.

 * The default value for pack.deltacachesize, used by "git repack", is now
   256M, instead of unbounded.  Otherwise a repack of a moderately sized
   repository would needlessly eat into swap.

 * Document how "git repack" (hence "git gc") interacts with a repository
   that borrows its objects from other repositories (e.g. ones created by
   "git clone -s").

 * "git show" on an annotated tag lacked a delimiting blank line between
   the tag itself and the contents of the object it tags.

 * "git verify-pack -v" erroneously reported number of objects with too
   deep delta depths as "chain length 0" objects.

 * Long names of authors and committers outside US-ASCII were sometimes
   incorrectly shown in "gitweb".

Other minor documentation updates are included.
Commit	Line	Data
d9b9784f JH	1	GIT v1.6.4.1 Release Notes
	2	==========================
	3
	4	Fixes since v1.6.4
	5	------------------
	6
	7	* An unquoted value in the configuration file, when it contains more than
	8	one whitespaces in a row, got them replaced with a single space.
	9
	10	* "git am" used to accept a single piece of e-mail per file (not a mbox)
	11	as its input, but multiple input format support in v1.6.4 broke it.
	12	Apparently many people have been depending on this feature.
	13
	14	* The short help text for "git filter-branch" command was a single long
	15	line, wrapped by terminals, and was hard to read.
	16
	17	* The "recursive" strategy of "git merge" segfaulted when a merge has
	18	more than one merge-bases, and merging of these merge-bases involves
	19	a rename/rename or a rename/add conflict.
	20
	21	* "git pull --rebase" did not use the right fork point when the
	22	repository has already fetched from the upstream that rewinds the
	23	branch it is based on in an earlier fetch.
	24
	25	* Explain the concept of fast-forward more fully in "git push"
	26	documentation, and hint to refer to it from an error message when the
	27	command refuses an update to protect the user.
	28
	29	* The default value for pack.deltacachesize, used by "git repack", is now
	30	256M, instead of unbounded. Otherwise a repack of a moderately sized
	31	repository would needlessly eat into swap.
	32
	33	* Document how "git repack" (hence "git gc") interacts with a repository
	34	that borrows its objects from other repositories (e.g. ones created by
	35	"git clone -s").
	36
	37	* "git show" on an annotated tag lacked a delimiting blank line between
	38	the tag itself and the contents of the object it tags.
	39
	40	* "git verify-pack -v" erroneously reported number of objects with too
	41	deep delta depths as "chain length 0" objects.
	42
	43	* Long names of authors and committers outside US-ASCII were sometimes
	44	incorrectly shown in "gitweb".
	45
	46	Other minor documentation updates are included.