Skip to content

Commit c5764c0

Browse files
committed
Merge branch 'maint'
* maint: git-show-ref.txt: remove word and make consistent git-svn documentation: fix typo in 'rebase vs. pull/merge' section
2 parents 2af202b + 3ba4f3a commit c5764c0

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

Documentation/git-show-ref.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The --exclude-existing form is a filter that does the inverse, it shows the
2424
refs from stdin that don't exist in the local repository.
2525

2626
Use of this utility is encouraged in favor of directly accessing files under
27-
in the `.git` directory.
27+
the `.git` directory.
2828

2929
OPTIONS
3030
-------
@@ -50,7 +50,7 @@ OPTIONS
5050
-s::
5151
--hash::
5252

53-
Only show the SHA1 hash, not the reference name. When also using
53+
Only show the SHA1 hash, not the reference name. When combined with
5454
--dereference the dereferenced tag will still be shown after the SHA1.
5555

5656
--verify::

Documentation/git-svn.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -623,7 +623,7 @@ pulled or merged from. This is because the author favored
623623
If you use `git svn set-tree A..B` to commit several diffs and you do
624624
not have the latest remotes/git-svn merged into my-branch, you should
625625
use `git svn rebase` to update your work branch instead of `git pull` or
626-
`git merge`. `pull`/`merge' can cause non-linear history to be flattened
626+
`git merge`. `pull`/`merge` can cause non-linear history to be flattened
627627
when committing into SVN, which can lead to merge commits reversing
628628
previous commits in SVN.
629629

0 commit comments

Comments
 (0)