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

Git v1.7.10.2 Release Notes
===========================

Fixes since v1.7.10.1
---------------------

 * The test scaffolding for git-daemon was flaky.

 * The test scaffolding for fast-import was flaky.

 * The filesystem boundary was not correctly reported when .git directory
   discovery stopped at a mount point.

 * HTTP transport that requires authentication did not work correctly when
   multiple connections are used simultaneously.

 * Minor memory leak during unpack_trees (hence "merge" and "checkout"
   to check out another branch) has been plugged.

 * In the older days, the header "Conflicts:" in "cherry-pick" and "merge"
   was separated by a blank line from the list of paths that follow for
   readability, but when "merge" was rewritten in C, we lost it by
   mistake. Remove the newline from "cherry-pick" to make them match
   again.

 * The command line parser choked "git cherry-pick $name" when $name can
   be both revision name and a pathname, even though $name can never be a
   path in the context of the command.

 * The "include.path" facility in the configuration mechanism added in
   1.7.10 forgot to interpret "~/path" and "~user/path" as it should.

 * "git config --rename-section" to rename an existing section into a
   bogus one did not check the new name.

 * The "diff --no-index" codepath used limited-length buffers, risking
   pathnames getting truncated.  Update it to use the strbuf API.

 * The report from "git fetch" said "new branch" even for a non branch
   ref.

 * The http-backend (the server side of the smart http transfer) used
   to overwrite GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL with the
   value obtained from REMOTE_USER unconditionally, making it
   impossible for the server side site-specific customization to use
   different identity sources to affect the names logged. It now uses
   REMOTE_USER only as a fallback value.

 * "log --graph" was not very friendly with "--stat" option and its
   output had line breaks at wrong places.

 * Octopus merge strategy did not reduce heads that are recorded in the
   final commit correctly.

 * "git push" over smart-http lost progress output a few releases ago;
   this release resurrects it.

 * The error and advice messages given by "git push" when it fails due
   to non-ff were not very helpful to new users; it has been broken
   into three cases, and each is given a separate advice message.

 * The insn sheet given by "rebase -i" did not make it clear that the
   insn lines can be re-ordered to affect the order of the commits in
   the resulting history.

 * "git repack" used to write out unreachable objects as loose objects
   when repacking, even if such loose objects will immediately pruned
   due to its age.

 * A contrib script "rerere-train" did not work out of the box unless
   user futzed with her $PATH.

 * "git rev-parse --show-prefix" used to emit nothing when run at the
   top-level of the working tree, but now it gives a blank line.

 * The i18n of error message "git stash save" was not properly done.

 * "git submodule" used a sed script that some platforms mishandled.

 * When using a Perl script on a system where "perl" found on user's
   $PATH could be ancient or otherwise broken, we allow builders to
   specify the path to a good copy of Perl with $PERL_PATH.  The
   gitweb test forgot to use that Perl when running its test.

Also contains minor fixes and documentation updates.
Commit	Line	Data
42325fb2 JH	1	Git v1.7.10.2 Release Notes
	2	===========================
	3
	4	Fixes since v1.7.10.1
	5	---------------------
	6
	7	* The test scaffolding for git-daemon was flaky.
	8
	9	* The test scaffolding for fast-import was flaky.
	10
	11	* The filesystem boundary was not correctly reported when .git directory
	12	discovery stopped at a mount point.
	13
	14	* HTTP transport that requires authentication did not work correctly when
	15	multiple connections are used simultaneously.
	16
b6555d73 JH	17	* Minor memory leak during unpack_trees (hence "merge" and "checkout"
	18	to check out another branch) has been plugged.
	19
42325fb2 JH	20	* In the older days, the header "Conflicts:" in "cherry-pick" and "merge"
	21	was separated by a blank line from the list of paths that follow for
	22	readability, but when "merge" was rewritten in C, we lost it by
	23	mistake. Remove the newline from "cherry-pick" to make them match
	24	again.
	25
	26	* The command line parser choked "git cherry-pick $name" when $name can
	27	be both revision name and a pathname, even though $name can never be a
	28	path in the context of the command.
	29
5ad3e16a JH	30	* The "include.path" facility in the configuration mechanism added in
	31	1.7.10 forgot to interpret "~/path" and "~user/path" as it should.
	32
42325fb2 JH	33	* "git config --rename-section" to rename an existing section into a
	34	bogus one did not check the new name.
	35
	36	* The "diff --no-index" codepath used limited-length buffers, risking
	37	pathnames getting truncated. Update it to use the strbuf API.
	38
	39	* The report from "git fetch" said "new branch" even for a non branch
	40	ref.
	41
5ad3e16a JH	42	* The http-backend (the server side of the smart http transfer) used
	43	to overwrite GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL with the
	44	value obtained from REMOTE_USER unconditionally, making it
	45	impossible for the server side site-specific customization to use
	46	different identity sources to affect the names logged. It now uses
	47	REMOTE_USER only as a fallback value.
	48
	49	* "log --graph" was not very friendly with "--stat" option and its
	50	output had line breaks at wrong places.
	51
42325fb2 JH	52	* Octopus merge strategy did not reduce heads that are recorded in the
	53	final commit correctly.
	54
5ad3e16a JH	55	* "git push" over smart-http lost progress output a few releases ago;
	56	this release resurrects it.
	57
b6555d73 JH	58	* The error and advice messages given by "git push" when it fails due
	59	to non-ff were not very helpful to new users; it has been broken
	60	into three cases, and each is given a separate advice message.
	61
5ad3e16a JH	62	* The insn sheet given by "rebase -i" did not make it clear that the
	63	insn lines can be re-ordered to affect the order of the commits in
	64	the resulting history.
	65
b6555d73 JH	66	* "git repack" used to write out unreachable objects as loose objects
	67	when repacking, even if such loose objects will immediately pruned
	68	due to its age.
	69
5ad3e16a JH	70	* A contrib script "rerere-train" did not work out of the box unless
	71	user futzed with her $PATH.
	72
b6555d73 JH	73	* "git rev-parse --show-prefix" used to emit nothing when run at the
	74	top-level of the working tree, but now it gives a blank line.
	75
42325fb2 JH	76	* The i18n of error message "git stash save" was not properly done.
42325fb2 JH	77
5ad3e16a JH	78	* "git submodule" used a sed script that some platforms mishandled.
5ad3e16a JH	79
42325fb2 JH	80	* When using a Perl script on a system where "perl" found on user's
	81	$PATH could be ancient or otherwise broken, we allow builders to
	82	specify the path to a good copy of Perl with $PERL_PATH. The
	83	gitweb test forgot to use that Perl when running its test.
	84
	85	Also contains minor fixes and documentation updates.