git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Dirson <ydirson@altern.org>
To: git@vger.kernel.org
Cc: Yann Dirson <ydirson@altern.org>
Subject: [PATCH 4/4] git-svn.txt: fix description of fetch flags accepted by clone.
Date: Mon,  6 Jul 2009 00:03:17 +0200	[thread overview]
Message-ID: <1246831397-19489-5-git-send-email-ydirson@altern.org> (raw)
In-Reply-To: <1246831397-19489-4-git-send-email-ydirson@altern.org>


Signed-off-by: Yann Dirson <ydirson@altern.org>
---
 Documentation/git-svn.txt |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 03bc1c1..1e56466 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -147,10 +147,10 @@ Skip "branches" and "tags" of first level directories;;
 	or if a second argument is passed; it will create a directory
 	and work within that.  It accepts all arguments that the
 	'init' and 'fetch' commands accept; with the exception of
-	'--fetch-all'.   After a repository is cloned, the 'fetch'
-	command will be able to update revisions without affecting
-	the working tree; and the 'rebase' command will be able
-	to update the working tree with the latest changes.
+	'--fetch-all' and '--parent'.  After a repository is cloned,
+	the 'fetch' command will be able to update revisions without
+	affecting the working tree; and the 'rebase' command will be
+	able to update the working tree with the latest changes.
 
 'rebase'::
 	This fetches revisions from the SVN parent of the current HEAD
-- 
1.6.3.3

  reply	other threads:[~2009-07-05 22:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 22:03 [PATCH 0/4] First set of improvements to git-svn user doc Yann Dirson
2009-07-05 22:03 ` [PATCH 1/4] git-svn.txt: stop using dash-form of commands Yann Dirson
2009-07-05 22:03   ` [PATCH 2/4] git-svn.txt: make formatting more consistent Yann Dirson
2009-07-05 22:03     ` [PATCH 3/4] git-svn.txt: fix fetch flags incorrectly documented as init flags Yann Dirson
2009-07-05 22:03       ` Yann Dirson [this message]
2009-07-06 22:20 ` [PATCH 0/4] First set of improvements to git-svn user doc Eric Wong
2009-07-07 13:02   ` [PATCHv2 " Yann Dirson
2009-07-07 13:02     ` [PATCH 1/4] git-svn.txt: stop using dash-form of commands Yann Dirson
2009-07-07 13:02       ` [PATCH 2/4] git-svn.txt: make formatting more consistent Yann Dirson
2009-07-07 13:02         ` [PATCH 3/4] git-svn.txt: fix fetch flags incorrectly documented as init flags Yann Dirson
2009-07-07 13:02           ` [PATCH 4/4] git-svn.txt: fix description of fetch flags accepted by clone Yann Dirson
2009-07-07 13:22   ` [PATCH 0/4] First set of improvements to git-svn user doc Yann Dirson
2009-07-07 20:22   ` [PATCHv3 " Yann Dirson
2009-07-07 20:22     ` [PATCH 1/4] git-svn.txt: stop using dash-form of commands Yann Dirson
2009-07-07 20:22       ` [PATCH 2/4] git-svn.txt: make formatting more consistent Yann Dirson
2009-07-07 20:22         ` [PATCH 3/4] git-svn.txt: fix fetch flags incorrectly documented as init flags Yann Dirson
2009-07-07 20:22           ` [PATCH 4/4] git-svn.txt: fix description of fetch flags accepted by clone Yann Dirson

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=1246831397-19489-5-git-send-email-ydirson@altern.org \
    --to=ydirson@altern.org \
    --cc=git@vger.kernel.org \
    /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).