aboutsummaryrefslogtreecommitdiff
path: root/Documentation/git-svn.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2009-06-20 23:48:46 -0700
committerJunio C Hamano <gitster@pobox.com>2009-06-20 23:48:46 -0700
commit3ba4f3a9fc68ba4c5a0064107e8993c5fc5b684f (patch)
treeae4db4348f007b3603534d720690869bc5c4b3e0 /Documentation/git-svn.txt
parentef52aafa0f8b1d34f2ecd9b58f2198711c87cab3 (diff)
parentcd12f536129357d5347c1953db69bde68b5f46c9 (diff)
downloadgit-3ba4f3a9fc68ba4c5a0064107e8993c5fc5b684f.tar.gz
git-3ba4f3a9fc68ba4c5a0064107e8993c5fc5b684f.tar.xz
Merge branch 'maint-1.6.2' into maint
* maint-1.6.2: 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/git-svn.txt')
-rw-r--r--Documentation/git-svn.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 1c4089466..74be8435c 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -615,7 +615,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.