aboutsummaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2009-06-20 23:48:28 -0700
committerJunio C Hamano <gitster@pobox.com>2009-06-20 23:48:28 -0700
commitcd12f536129357d5347c1953db69bde68b5f46c9 (patch)
tree534f1f620a07c4d6d40eec15bc1178a06adef49b /Documentation
parent9b7dc7183528d42c46786a0be1acc58d4cd1f47a (diff)
parent4258c212ca2c3674be4b7e00a19db705eee77a48 (diff)
downloadgit-cd12f536129357d5347c1953db69bde68b5f46c9.tar.gz
git-cd12f536129357d5347c1953db69bde68b5f46c9.tar.xz
Merge branch 'maint-1.6.1' into maint-1.6.2
* maint-1.6.1: git-show-ref.txt: remove word and make consistent git-svn documentation: fix typo in 'rebase vs. pull/merge' section use xstrdup, not strdup in ll-merge.c
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-show-ref.txt4
-rw-r--r--Documentation/git-svn.txt2
2 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt
index 2f173fff3..98e294aa8 100644
--- a/Documentation/git-show-ref.txt
+++ b/Documentation/git-show-ref.txt
@@ -24,7 +24,7 @@ The --exclude-existing form is a filter that does the inverse, it shows the
refs from stdin that don't exist in the local repository.
Use of this utility is encouraged in favor of directly accessing files under
-in the `.git` directory.
+the `.git` directory.
OPTIONS
-------
@@ -50,7 +50,7 @@ OPTIONS
-s::
--hash::
- Only show the SHA1 hash, not the reference name. When also using
+ Only show the SHA1 hash, not the reference name. When combined with
--dereference the dereferenced tag will still be shown after the SHA1.
--verify::
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index cda338933..d8bf7bfc3 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -599,7 +599,7 @@ pulled or merged from. This is because the author favored
If you use `git svn set-tree A..B` to commit several diffs and you do
not have the latest remotes/git-svn merged into my-branch, you should
use `git svn rebase` to update your work branch instead of `git pull` or
-`git merge`. `pull`/`merge' can cause non-linear history to be flattened
+`git merge`. `pull`/`merge` can cause non-linear history to be flattened
when committing into SVN, which can lead to merge commits reversing
previous commits in SVN.