Thread (4 messages) flat view 4 messages, 4 authors, 2016-08-13

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

From: Deskin Miller <hidden>
Date: 2016-06-15 22:45:33

On Thu, Oct 30, 2008 at 06:08:20PM +0200, _vi@list.ru wrote:
quoted hunk ↗ jump to hunk
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.
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help