mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

RelNotes/1.8.0: various typo and style fixes

Browse Source 
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Michael J Gruber
2012-10-02 16:35:55 +02:00
committed by Junio C Hamano
parent b0ec16b49e
commit d117dd2096
1 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
Documentation/RelNotes/1.8.0.txt
View File

@ -4,11 +4,11 @@ Git v1.8.0 Release Notes
Backward compatibility notes Backward compatibility notes
---------------------------- ----------------------------
In the next major release, we will change the behaviour of the "git In the next major release, we will change the behavior of the "git
push" command. When "git push [$there]" does not say what to push, we push" command. When "git push [$there]" does not say what to push, we
have used the traditional "matching" semantics (all your branches were have used the traditional "matching" semantics so far (all your branches were
sent to the remote as long as there already are branches of the same sent to the remote as long as there already are branches of the same
name over there). We will use the "simple" semantics, that pushes the name over there). We will now use the "simple" semantics, that pushes the
current branch to the branch with the same name only when the current current branch to the branch with the same name only when the current
branch is set to integrate with that remote branch. There is a user branch is set to integrate with that remote branch. There is a user
preference configuration variable "push.default" to change this, and preference configuration variable "push.default" to change this, and
@ -33,9 +33,9 @@ UI, Workflows & Features
* A credential helper to allow access to the Gnome keyring has been * A credential helper to allow access to the Gnome keyring has been
added. added.
* When "git am" sanitizes the Subject: line, we strip the prefix from * When "git am" sanitizes the "Subject:" line, we strip the prefix from
"Re: subject" and also from a less common "re: subject", but left "Re: subject" and also from a less common "re: subject", but left
even less common "RE: subject" intact. the even less common "RE: subject" intact. We strip that now, too.
* It was tempting to say "git branch --set-upstream origin/master", * It was tempting to say "git branch --set-upstream origin/master",
but that tells Git to arrange the local branch "origin/master" to but that tells Git to arrange the local branch "origin/master" to
@ -57,15 +57,15 @@ UI, Workflows & Features
repository path, etc. repository path, etc.
* "git difftool --dir-diff" learned to use symbolic links to prepare * "git difftool --dir-diff" learned to use symbolic links to prepare
temporary copy of the working tree when available. a temporary copy of the working tree when available.
* "git grep" learned to use a non-standard pattern type by default if * "git grep" learned to use a non-standard pattern type by default if
a configuration variable tells it to. a configuration variable tells it to.
* "git merge-base" learned "--is-ancestor A B" option to tell if A is * "git merge-base" learned the "--is-ancestor A B" option to tell if A is
an ancestor of B. The result is indicated by its exit status code. an ancestor of B. The result is indicated by its exit status code.
* "git mergetool" allows users to override the actual command used * "git mergetool" now allows users to override the actual command used
with the mergetool.$name.cmd configuration variable even for built-in with the mergetool.$name.cmd configuration variable even for built-in
mergetool backends. mergetool backends.
@ -73,14 +73,14 @@ UI, Workflows & Features
effect even on binary files. effect even on binary files.
* "git rebase -i" learned the "--edit-todo" option to open an editor * "git rebase -i" learned the "--edit-todo" option to open an editor
to edit the insn sheet. to edit the instruction sheet.
Foreign Interface Foreign Interface
* "git svn" has been updated to work with SVN 1.7. * "git svn" has been updated to work with SVN 1.7.
* "git p4" learned "--conflicts" option to specify what to do when * "git p4" learned the "--conflicts" option to specify what to do when
encountering a conflict during "p4 submit". encountering a conflict during "p4 submit".
@ -88,12 +88,12 @@ Performance, Internal Implementation, etc. (please report possible regressions)
* Git ships with a fall-back regexp implementation for platforms with * Git ships with a fall-back regexp implementation for platforms with
buggy regexp library, but it was easy for people to keep using their buggy regexp library, but it was easy for people to keep using their
platform regexp. A new test has been added to check this. platform regexp by mistake. A new test has been added to check this.
* The "check-docs" build target has been updated and greatly * The "check-docs" build target has been updated and greatly
simplified. simplified.
* The test suite is run under MALLOC_CHECK_ when running with glibc * The test suite is run under MALLOC_CHECK_ when running with a glibc
that supports the feature. that supports the feature.
* The documentation in the TeXinfo format was using indented output * The documentation in the TeXinfo format was using indented output
@ -101,7 +101,7 @@ Performance, Internal Implementation, etc. (please report possible regressions)
monospace. monospace.
* Compatibility wrapper around some mkdir(2) implementations that * Compatibility wrapper around some mkdir(2) implementations that
reject parameter with trailing slash has been introduced. reject parameters with trailing slash has been introduced.
* Compatibility wrapper for systems that lack usable setitimer() has * Compatibility wrapper for systems that lack usable setitimer() has
been added. been added.
@ -113,7 +113,7 @@ Performance, Internal Implementation, etc. (please report possible regressions)
when the user says "git checkout -b -t foo bar" (e.g. "-t" is not a when the user says "git checkout -b -t foo bar" (e.g. "-t" is not a
good name for a branch). good name for a branch).
* Many internal uses of "git merge-base" equivalent were only to see * Many internal uses of a "git merge-base" equivalent were only to see
if one commit fast-forwards to the other, which did not need the if one commit fast-forwards to the other, which did not need the
full set of merge bases to be computed. They have been updated to full set of merge bases to be computed. They have been updated to
use less expensive checks. use less expensive checks.
@ -164,7 +164,7 @@ to them for details).
* Output from "git branch -v" contains "(no branch)" that could be * Output from "git branch -v" contains "(no branch)" that could be
localized, but the code to align it along with the names of localized, but the code to align it along with the names of
branches were counting in bytes, not in display columns. branches was counting in bytes, not in display columns.
* "git cherry-pick A C B" used to replay changes in A and then B and * "git cherry-pick A C B" used to replay changes in A and then B and
then C if these three commits had committer timestamps in that then C if these three commits had committer timestamps in that
@ -189,11 +189,11 @@ to them for details).
* Earlier we made the diffstat summary line that shows the number of * Earlier we made the diffstat summary line that shows the number of
lines added/deleted localizable, but it was found irritating having lines added/deleted localizable, but it was found irritating having
to see them in various languages on a list whose discussion language to see them in various languages on a list whose discussion language
is English. is English, and this change has been reverted.
* "git fetch --all", when passed "--no-tags", did not honor the * "git fetch --all", when passed "--no-tags", did not honor the
"--no-tags" option while fetching from individual remotes (the same "--no-tags" option while fetching from individual remotes (the same
issue existed with "--tags", but combination "--all --tags" makes issue existed with "--tags", but the combination "--all --tags" makes
much less sense than "--all --no-tags"). much less sense than "--all --no-tags").
* "git fetch" over http had an old workaround for an unlikely server * "git fetch" over http had an old workaround for an unlikely server
@ -202,13 +202,13 @@ to them for details).
(merge 6ac964a sp/maint-http-info-refs-no-retry later to maint). (merge 6ac964a sp/maint-http-info-refs-no-retry later to maint).
* "git fetch" over http advertised that it supports "deflate", which * "git fetch" over http advertised that it supports "deflate", which
is much less common, and did not advertise more common "gzip" on is much less common, and did not advertise the more common "gzip" on
its Accept-Encoding header. its Accept-Encoding header.
(merge aa90b96 sp/maint-http-enable-gzip later to maint). (merge aa90b96 sp/maint-http-enable-gzip later to maint).
* After "gitk" showed the contents of a tag, neither "Reread * After "gitk" showed the contents of a tag, neither "Reread
references" nor "Reload" did not update what is shown as the references" nor "Reload" updated what is shown as the
contents of it, when the user overwrote the tag with "git tag -f". contents of it when the user overwrote the tag with "git tag -f".
* "git log --all-match --grep=A --grep=B" ought to show commits that * "git log --all-match --grep=A --grep=B" ought to show commits that
mention both A and B, but when these three options are used with mention both A and B, but when these three options are used with
@ -224,21 +224,21 @@ to them for details).
(merge 74eb32d jk/receive-pack-unpack-error-to-pusher later to maint). (merge 74eb32d jk/receive-pack-unpack-error-to-pusher later to maint).
* When you misspell the command name you give to the "exec" action in * When you misspell the command name you give to the "exec" action in
the "git rebase -i" insn sheet, you are told that 'rebase' is not a the "git rebase -i" instruction sheet you were told that 'rebase' is not a
git subcommand from "git rebase --continue". git subcommand from "git rebase --continue".
* The subcommand in "git remote" to remove a defined remote was * The subcommand in "git remote" to remove a defined remote was
"rm" and the command did not take a fully-spelled "remove". "rm" and the command did not take a fully-spelled "remove".
* The interactive prompt "git send-email" gives was error prone. It * The interactive prompt that "git send-email" gives was error prone. It
asked "What e-mail address do you want to use?" with the address it asked "What e-mail address do you want to use?" with the address it
guessed (correctly) the user would want to use in its prompt, guessed (correctly) the user would want to use in its prompt,
tempting the user to say "y". But the response was taken as "No, tempting the user to say "y". But the response was taken as "No,
please use 'y' as the e-mail address instead", which is most please use 'y' as the e-mail address instead", which is most
certainly not what the user meant. certainly not what the user meant.
* "git show --format='%ci'" did not give timestamp correctly for * "git show --format='%ci'" did not give the timestamp correctly for
commits created without human readable name on "committer" line. commits created without human readable name on the "committer" line.
* "git show --quiet" ought to be a synonym for "git show -s", but * "git show --quiet" ought to be a synonym for "git show -s", but
wasn't. wasn't.