[PATCH] Documented --no-checkout option in git-svn

From: Vitaly "_Vi" Shukela <redacted>

Signed-off-by: Vitaly "_Vi" Shukela <redacted>
---
 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..90784a5 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 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 latest revision after fetching.
+
 'rebase'::
 	This fetches revisions from the SVN parent of the current HEAD
 	and rebases the current (uncommitted to SVN) work against it.

-- 
1.5.6.5

On Thu, Oct 30, 2008 at 06:08:20PM +0200, _vi@list.ru wrote:

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.

Deskin Miller

OK, agree with all changes. This is my the first patch.
/* not including the patch text as it gets broken by Iceweasel. */

Sam Vilain wrote:

I think the wording is close enough; here's a version which looks good
to me and fixes the asciidoc differences.
  

On Thu, 2008-10-30 at 14:07 -0400, Deskin Miller wrote:

quoted

+--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 <redacted>

Signed-off-by: Vitaly "_Vi" Shukela <redacted>
Signed-off-by: Sam Vilain <redacted>
---
 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