From: Sam Vilain <sam@vilain.net>
To: git@vger.kernel.org
To: Deskin Miller <deskinm@umich.edu>
Cc: Sam Vilain <sam@vilain.net>,
"_vi@list.ru, git@vger.kernel.org, gitster@pobox.com,
Vitaly _Vi Shukela" <public_vi@tut.by>,
"Vitaly \"_Vi\" Shukela" <public_vi@tut.by>
Subject: Re: [PATCH] Documented --no-checkout option in git-svn
Date: Thu, 30 Oct 2008 11:20:41 -0700 [thread overview]
Message-ID: <1225390505.19891.41.camel@maia.lan> (raw)
In-Reply-To: <20081030180736.GA20322@euler>
On Thu, 2008-10-30 at 14:07 -0400, Deskin Miller wrote:
> > +--no-checkout
> > + Do not checkout latest revision after fetching.
>
> This isn't quite how the other options are listed in the source; for one, this
> ends up formatted in the final manpage like
>
> --no-checkout Do not checkout latest revision after fetching.
>
> Instead of
>
> --no-checkout
> Do not checkout latest revision after fetching.
>
> Also, the wording seems slightly imprecise; in fact, if the repository already
> has a checkout, git svn fetch would not attempt to check anything out in its
> place, nor will it check anything out if there is a local master branch
> already. With clone this is not typically a problem, but in fact it is
> possible to clone into a preexisting git repository, so the same concerns
> exist.
I think the wording is close enough; here's a version which looks good
to me and fixes the asciidoc differences.
Subject: git-svn: document --no-checkout option
From: Vitaly "_Vi" Shukela <public_vi@tut.by>
Signed-off-by: Vitaly "_Vi" Shukela <public_vi@tut.by>
Signed-off-by: Sam Vilain <sam@vilain.net>
---
Documentation/git-svn.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 84c8f3c..2298512 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -91,6 +91,9 @@ COMMANDS
tracking. The name of the [svn-remote "..."] section in the
.git/config file may be specified as an optional command-line
argument.
+
+--no-checkout;;
+ Do not checkout the latest revision after fetching.
'clone'::
Runs 'init' and 'fetch'. It will automatically create a
@@ -103,6 +106,9 @@ COMMANDS
the working tree; and the 'rebase' command will be able
to update the working tree with the latest changes.
+--no-checkout;;
+ Do not checkout the latest revision after cloning.
+
'rebase'::
This fetches revisions from the SVN parent of the current HEAD
and rebases the current (uncommitted to SVN) work against it.
--
debian.1.5.6.1
next prev parent reply other threads:[~2008-10-30 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 16:08 [PATCH] Documented --no-checkout option in git-svn _vi
2008-10-30 18:07 ` Deskin Miller
2008-10-30 18:20 ` Sam Vilain [this message]
2008-10-31 22:36 ` public_vi
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=1225390505.19891.41.camel@maia.lan \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=public_vi@tut.by \
/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).