[PATCH] git-svn: clarify documentation of dcommit sub-command
- From
Jon Seymour <jon.seymour@gmail.com>
- Date
- May 7, 2012, 13:48 UTC
- Message-ID
- <1336398527-4363-1-git-send-email-jon.seymour@gmail.com>
Clarify that the optional "revision or branch" argument on dcommit sub-command refers to a git branch not an SVN branch.
If the user's intent is to commit the current series of commits onto a specific SVN branch rather than the trunk, the existing wording might lead them to believe that the optional argument may be a means to achieve this.
The rewording clarifies that the optional argument actually refers to the source git branch, not the target svn branch.
Signed-off-by: Jon Seymour <jon.seymour@gmail.com> --- Documentation/git-svn.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt index 34ee785..c516283 100644 --- a/Documentation/git-svn.txt +++ b/Documentation/git-svn.txt @@ -197,7 +197,7 @@ and have no uncommitted changes. pull or merge) your commits against the latest changes in the SVN repository. An optional revision or branch argument may be specified, and - causes 'git svn' to do all work on that revision/branch + causes 'git svn' to do all work on that git revision/branch instead of HEAD. This is advantageous over 'set-tree' (below) because it produces cleaner, more linear history.
-- 1.7.9.264.g3fbfe6