Skip to content

Commit f937421

Browse files
Michael J Grubergitster
authored andcommitted
Documentation: minor fixes to RelNotes-1.7.0
Signed-off-by: Michael J Gruber <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 85f6b43 commit f937421

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

Documentation/RelNotes-1.7.0.txt

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Git v1.7.0 Release Notes
44
Notes on behaviour change
55
-------------------------
66

7-
* "git push" into a branch that is currently checked out (i.e. pointed by
7+
* "git push" into a branch that is currently checked out (i.e. pointed at by
88
HEAD in a repository that is not bare) is refused by default.
99

1010
Similarly, "git push $there :$killed" to delete the branch $killed
@@ -19,7 +19,7 @@ Notes on behaviour change
1919
patch series with more than two messages. All messages will be sent
2020
as a reply to the first message, i.e. cover letter.
2121

22-
It has been possible to configure send-email to send "shallow thread"
22+
It has been possible already to configure send-email to send "shallow thread"
2323
by setting sendemail.chainreplyto configuration variable to false. The
2424
only thing this release does is to change the default when you haven't
2525
configured that variable.
@@ -30,7 +30,7 @@ Notes on behaviour change
3030
* "git diff" traditionally treated various "ignore whitespace" options
3131
only as a way to filter the patch output. "git diff --exit-code -b"
3232
exited with non-zero status even if all changes were about changing the
33-
ammount of whitespace and nothing else. and "git diff -b" showed the
33+
amount of whitespace and nothing else; and "git diff -b" showed the
3434
"diff --git" header line for such a change without patch text.
3535

3636
In this release, the "ignore whitespaces" options affect the semantics
@@ -106,7 +106,7 @@ Updates since v1.6.6
106106
defaults to the current branch, so "git fetch && git merge @{upstream}"
107107
will be equivalent to "git pull".
108108

109-
* "git branch --set-upstream" can be used to update the (surprise!) upstream
109+
* "git branch --set-upstream" can be used to update the (surprise!) upstream,
110110
i.e. where the branch is supposed to pull and merge from (or rebase onto).
111111

112112
* "git checkout A...B" is a way to detach HEAD at the merge base between
@@ -133,7 +133,7 @@ Updates since v1.6.6
133133
* "git fetch --all" can now be used in place of "git remote update".
134134

135135
* "git grep" does not rely on external grep anymore. It can use more than
136-
one threads to accelerate the operation.
136+
one thread to accelerate the operation.
137137

138138
* "git grep" learned "--quiet" option.
139139

@@ -159,13 +159,13 @@ Updates since v1.6.6
159159
* "git rebase --onto A...B" means the history is replayed on top of the
160160
merge base between A and B.
161161

162-
* "git rebase -i" learned new action "fixup", that squashes the change
162+
* "git rebase -i" learned new action "fixup" that squashes the change
163163
but does not affect existing log message.
164164

165-
* "git rebase -i" also learned --autosquash option, that is useful
165+
* "git rebase -i" also learned --autosquash option that is useful
166166
together with the new "fixup" action.
167167

168-
* "git remote" learned set-url subcommand, to update (surprise!) url
168+
* "git remote" learned set-url subcommand that updates (surprise!) url
169169
for an existing remote nickname.
170170

171171
* "git rerere" learned "forget path" subcommand. Together with "git

0 commit comments

Comments
 (0)