kernel
/
git
mirror of https://git.kernel.org/pub/scm/git/git.git
1
0
Fork 0
Code Releases Activity

clean up 1.5.4 release notes 

Mostly typo and small grammatical fixes with one or two rewordings for
clarity.  But note the important fix for status.relativepaths.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Jeff King 2007-12-20 07:11:25 -05:00 committed by Junio C Hamano
parent cdd859159e
commit 6a7f14c465
1 changed files with 17 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
Documentation/RelNotes-1.5.4.txt
View File

@ -14,28 +14,28 @@ Removal
Deprecation notices Deprecation notices
------------------- -------------------


* Next feature release of git (this change is scheduled for v1.6.0) * The next feature release of git (this change is scheduled for v1.6.0)
will by default install dashed form of commands (e.g. "git-commit") will by default install dashed form of commands (e.g. "git-commit")
outside of users' normal $PATH, and will install only selected outside of users' normal $PATH, and will install only selected
commands ("git" itself, and "gitk") in $PATH. This implies: commands ("git" itself, and "gitk") in $PATH. This implies:


- Using dashed form of git commands (e.g. "git-commit") from the - Using dashed forms of git commands (e.g. "git-commit") from the
command line has been informally deprecated since early 2006, but command line has been informally deprecated since early 2006, but
now it officially is, and will be removed in the future. Use now it officially is, and will be removed in the future. Use
dashless form (e.g. "git commit") instead. dashless forms (e.g. "git commit") instead.


- Using dashed from from your scripts, without first prepending the - Using dashed forms from your scripts, without first prepending the
return value from "git --exec-path" to the scripts' PATH, has been return value from "git --exec-path" to the scripts' PATH, has been
informally deprecated since early 2006, but now it officially is. informally deprecated since early 2006, but now it officially is.


- Use of dashed form with "PATH=$(git --exec-path):$PATH; export - Use of dashed forms with "PATH=$(git --exec-path):$PATH; export
PATH" early in your script is not deprecated with this change. PATH" early in your script is not deprecated with this change.


Users are strongly encouraged to adjust their habits and scripts now Users are strongly encouraged to adjust their habits and scripts now
to prepare for this. to prepare for this.


* The post-receive hook was introduced in March 2007 to supersede * The post-receive hook was introduced in March 2007 to supersede
post-update hook, primarily to overcome the command line length the post-update hook, primarily to overcome the command line length
limitation of the latter. Use of post-update hook will be deprecated limitation of the latter. Use of post-update hook will be deprecated
in future versions of git, starting from v1.6.0. in future versions of git, starting from v1.6.0.


@ -43,10 +43,11 @@ Deprecation notices
option, and will be removed in the future. option, and will be removed in the future.


* "git peek-remote" is deprecated, as "git ls-remote" was written in C * "git peek-remote" is deprecated, as "git ls-remote" was written in C
and works for all transports, and will be removed in the future. and works for all transports; "git peek-remote" will be removed in
the future.


* From v1.6.0, the repack.usedeltabaseoffset config option will default * From v1.6.0, the repack.usedeltabaseoffset config option will default
to true, which will give denser packfile (i.e. more efficient storage). to true, which will give denser packfiles (i.e. more efficient storage).
The downside is that git older than version 1.4.4 will not be able The downside is that git older than version 1.4.4 will not be able
to directly use a repository packed using this setting. to directly use a repository packed using this setting.


@ -67,7 +68,7 @@ Updates since v1.5.3
* gitk is now merged as a subdirectory of git.git project, in * gitk is now merged as a subdirectory of git.git project, in
preparation for its i18n. preparation for its i18n.


* progress display from many commands are a lot nicer to the eye. * progress displays from many commands are a lot nicer to the eye.
Transfer commands show throughput data. Transfer commands show throughput data.


* many commands that pay attention to per-directory .gitignore now do * many commands that pay attention to per-directory .gitignore now do
@ -76,12 +77,12 @@ Updates since v1.5.3
* Output processing for '--pretty=format:<user format>' has been * Output processing for '--pretty=format:<user format>' has been
optimized. optimized.


* Rename detection of diff family, while detecting exact matches, has * Rename detection of diff family while detecting exact matches has
been greatly optimized. been greatly optimized.


* Rename detection of diff family tries to make more naturally looking * Rename detection of diff family tries to make more natural looking
pairing. Earlier if more than one identical rename sources were pairing. Earlier, if multiple identical rename sources were
found in the preimage, they were picked pretty much at random. found in the preimage, the source used was picked pretty much at random.


* Value "true" for color.diff and color.status configuration used to * Value "true" for color.diff and color.status configuration used to
mean "always" (even when the output is not going to a terminal). mean "always" (even when the output is not going to a terminal).
@ -114,7 +115,7 @@ Updates since v1.5.3


* "git rebase --interactive" mode can now work on detached HEAD. * "git rebase --interactive" mode can now work on detached HEAD.


* Other minor to serious bugs in "git rebase -i" has been fixed. * Other minor to serious bugs in "git rebase -i" have been fixed.


* "git rebase" now detaches head during its operation, so after a * "git rebase" now detaches head during its operation, so after a
successful "git rebase" operation, the reflog entry branch@{1} for successful "git rebase" operation, the reflog entry branch@{1} for
@ -247,7 +248,7 @@ Updates since v1.5.3
* The format "git show" outputs an annotated tag has been updated to * The format "git show" outputs an annotated tag has been updated to
include "Tagger: " and "Date: " lines from the tag itself. Strictly include "Tagger: " and "Date: " lines from the tag itself. Strictly
speaking this is a backward incompatible change, but this is a speaking this is a backward incompatible change, but this is a
reasonable usability fix and people's script shouldn't have been reasonable usability fix and people's scripts shouldn't have been
relying on the exact output from "git show" Porcelain anyway. relying on the exact output from "git show" Porcelain anyway.


* "git cvsexportcommit" learned -w option to specify and switch to the * "git cvsexportcommit" learned -w option to specify and switch to the
@ -283,7 +284,7 @@ Updates since v1.5.3
makes copy-and-pasting for git-checkout/git-add/git-rm easier. The makes copy-and-pasting for git-checkout/git-add/git-rm easier. The
traditional behaviour to show the full path relative to the top of traditional behaviour to show the full path relative to the top of
the work tree can be had by setting status.relativepaths the work tree can be had by setting status.relativepaths
configuration variable to true. configuration variable to false.


* "git blame" kept text for each annotated revision in core needlessly; * "git blame" kept text for each annotated revision in core needlessly;
this has been corrected. this has been corrected.