From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Cc: trast@student.ethz.ch, Jon Seymour <jon.seymour@gmail.com>
Subject: [PATCH] git-svn: clarify documentation of dcommit sub-command
Date: Mon, 7 May 2012 19:18:47 +0530 [thread overview]
Message-ID: <1336398527-4363-1-git-send-email-jon.seymour@gmail.com> (raw)
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
next reply other threads:[~2012-05-07 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 13:48 Jon Seymour [this message]
2012-05-09 17:19 ` [PATCH] git-svn: clarify documentation of dcommit sub-command Junio C Hamano
2012-05-10 19:13 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1336398527-4363-1-git-send-email-jon.seymour@gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).