[PATCH] Documentation: Remove mentions of git-svnimport.

Subsystems: documentation, the rest

DORMANTno replies

3 messages, 2 authors, 2016-06-15 · open the first message on its own page

[PATCH] Documentation: Remove mentions of git-svnimport.

From: Brian Gernhardt <hidden>
Date: 2016-06-15 22:45:04

git-svnimport is no longer supported, so don't mention it in the
documentation.  This also updates the description, removing the
historical discussion, since it mostly dealt with how it differed from
svnimport.

Noticed by Jurko Gospodnetić [off-list ref]

Signed-off-by: Brian Gernhardt <redacted>
---
 Documentation/git-svn.txt |   22 ++++++----------------
 1 files changed, 6 insertions(+), 16 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index e7c0f1c..4d82a08 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -12,18 +12,10 @@ SYNOPSIS
 DESCRIPTION
 -----------
 'git-svn' is a simple conduit for changesets between Subversion and git.
-It is not to be confused with linkgit:git-svnimport[1], which is
-read-only.
-
-'git-svn' was originally designed for an individual developer who wants a
-bidirectional flow of changesets between a single branch in Subversion
-and an arbitrary number of branches in git.  Since its inception,
-'git-svn' has gained the ability to track multiple branches in a manner
-similar to 'git-svnimport'.
-
-'git-svn' is especially useful when it comes to tracking repositories
-not organized in the way Subversion developers recommend (trunk,
-branches, tags directories).
+It provides a bidirectional flow of changes between a Subversion and a git
+respository.  'git-svn' is especially useful when it comes to tracking
+repositories not organized in the way Subversion developers recommend
+(trunk, branches, tags directories).
 
 COMMANDS
 --------
@@ -218,8 +210,7 @@ Any other arguments are passed directly to 'git-log'
 
 'commit-diff'::
 	Commits the diff of two tree-ish arguments from the
-	command-line.  This command is intended for interoperability with
-	'git-svnimport' and does not rely on being inside an `git-svn
+	command-line.  This command does not rely on being inside an `git-svn
 	init`-ed repository.  This command takes three arguments, (a) the
 	original tree to diff against, (b) the new tree result, (c) the
 	URL of the target Subversion repository.  The final argument
@@ -317,8 +308,7 @@ config key: svn.findcopiesharder
 -A<filename>::
 --authors-file=<filename>::
 
-Syntax is compatible with the files used by 'git-svnimport' and
-'git-cvsimport':
+Syntax is compatible with the file used by 'git-cvsimport':
 
 ------------------------------------------------------------------------
 	loginname = Joe User <user@example.com>
-- 
1.6.0.rc1.154.ge3fc

Re: [PATCH] Documentation: Remove mentions of git-svnimport.

From: Pieter de Bie <hidden>
Date: 2016-06-15 22:45:04

On Jul 30, 2008, at 2:38 AM, Brian Gernhardt wrote:
+respository.  'git-svn' is especially useful when it comes to  
tracking
+repositories not organized in the way Subversion developers recommend
+(trunk, branches, tags directories).
This is of course not true. Git svn is especially useful when branches  
_are_ organized
that way, but other configurations are somewhat supported. This  
comment still refers
to the comparison with svnimport.

Re: [PATCH] Documentation: Remove mentions of git-svnimport.

From: Brian Gernhardt <hidden>
Date: 2016-06-15 22:45:04

On Jul 29, 2008, at 8:44 PM, Pieter de Bie wrote:
On Jul 30, 2008, at 2:38 AM, Brian Gernhardt wrote:
quoted
+respository.  'git-svn' is especially useful when it comes to  
tracking
+repositories not organized in the way Subversion developers  
recommend
+(trunk, branches, tags directories).
This is of course not true. Git svn is especially useful when  
branches _are_ organized
that way, but other configurations are somewhat supported. This  
comment still refers
to the comparison with svnimport.
The original statement was in a paragraph by itself, so I assumed it  
was a not a comparison.  Reading it again, I can see your point.

~~ Brian
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help