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

Git v1.7.4.4 Release Notes
==========================

Fixes since v1.7.4.3
--------------------

 * Compilation of sha1_file.c on BSD platforms were broken due to our
   recent use of getrlimit() without including <sys/resource.h>.

 * "git config" did not diagnose incorrect configuration variable names.

 * "git format-patch" did not wrap a long subject line that resulted from
   rfc2047 encoding.

 * "git instaweb" should work better again with plackup.

 * "git log --max-count=4 -Sfoobar" now shows 4 commits that changes the
   number of occurrences of string "foobar"; it used to scan only for 4
   commits and then emitted only matching ones.

 * "git log --first-parent --boundary $c^..$c" segfaulted on a merge.

 * "git pull" into an empty branch should have behaved as if
   fast-forwarding from emptiness to the version being pulled, with
   the usual protection against overwriting untracked files.

 * "git submodule" that is run while a merge in the superproject is in
   conflicted state tried to process each conflicted submodule up to
   three times.

 * "git status" spent all the effort to notice racily-clean index entries
   but didn't update the index file to help later operations go faster in
   some cases.

And other minor fixes and documentation updates.
Commit	Line	Data
8e848868 JH	1	Git v1.7.4.4 Release Notes
	2	==========================
	3
	4	Fixes since v1.7.4.3
	5	--------------------
	6
	7	* Compilation of sha1_file.c on BSD platforms were broken due to our
	8	recent use of getrlimit() without including <sys/resource.h>.
	9
	10	* "git config" did not diagnose incorrect configuration variable names.
	11
	12	* "git format-patch" did not wrap a long subject line that resulted from
	13	rfc2047 encoding.
	14
	15	* "git instaweb" should work better again with plackup.
	16
	17	* "git log --max-count=4 -Sfoobar" now shows 4 commits that changes the
	18	number of occurrences of string "foobar"; it used to scan only for 4
	19	commits and then emitted only matching ones.
	20
	21	* "git log --first-parent --boundary $c^..$c" segfaulted on a merge.
	22
	23	* "git pull" into an empty branch should have behaved as if
	24	fast-forwarding from emptiness to the version being pulled, with
	25	the usual protection against overwriting untracked files.
	26
5fb41b88 JH	27	* "git submodule" that is run while a merge in the superproject is in
	28	conflicted state tried to process each conflicted submodule up to
	29	three times.
	30
8e848868 JH	31	* "git status" spent all the effort to notice racily-clean index entries
	32	but didn't update the index file to help later operations go faster in
	33	some cases.
	34
	35	And other minor fixes and documentation updates.