undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: Remove mentions of git-svnimport.

Browse Source 
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.  The new description gives some starting points into the
rest of the documentation.

Noticed by Jurko Gospodnetić <jurko.gospodnetic@docte.hr>

Signed-off-by: Brian Gernhardt <benji@silverinsanity.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Brian Gernhardt 2008-07-29 21:16:01 -04:00 committed by Junio C Hamano
parent 2c9693bda5
commit 8cb070a4cf
1 changed files with 12 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
Documentation/git-svn.txt
View File

@ -12,18 +12,18 @@ SYNOPSIS
DESCRIPTION DESCRIPTION
----------- -----------
'git-svn' is a simple conduit for changesets between Subversion and git. '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 It provides a bidirectional flow of changes between a Subversion and a git
read-only. respository.
'git-svn' was originally designed for an individual developer who wants a 'git-svn' can track a single Subversion branch simply by using a
bidirectional flow of changesets between a single branch in Subversion URL to the branch, follow branches laid out in the Subversion recommended
and an arbitrary number of branches in git. Since its inception, method (trunk, branches, tags directories) with the --stdlayout option, or
'git-svn' has gained the ability to track multiple branches in a manner follow branches in any layout with the -T/-t/-b options (see options to
similar to 'git-svnimport'. 'init' below, and also the 'clone' command).
'git-svn' is especially useful when it comes to tracking repositories Once tracking a Subversion branch (with any of the above methods), the git
not organized in the way Subversion developers recommend (trunk, repository can be updated from Subversion by the 'fetch' command and
branches, tags directories). Subversion updated from git by the 'dcommit' command.
COMMANDS COMMANDS
-------- --------
@ -218,8 +218,7 @@ Any other arguments are passed directly to 'git-log'
'commit-diff':: 'commit-diff'::
Commits the diff of two tree-ish arguments from the Commits the diff of two tree-ish arguments from the
command-line. This command is intended for interoperability with command-line. This command does not rely on being inside an `git-svn
'git-svnimport' and does not rely on being inside an `git-svn
init`-ed repository. This command takes three arguments, (a) the init`-ed repository. This command takes three arguments, (a) the
original tree to diff against, (b) the new tree result, (c) the original tree to diff against, (b) the new tree result, (c) the
URL of the target Subversion repository. The final argument URL of the target Subversion repository. The final argument
@ -317,8 +316,7 @@ config key: svn.findcopiesharder
-A<filename>:: -A<filename>::
--authors-file=<filename>:: --authors-file=<filename>::
Syntax is compatible with the files used by 'git-svnimport' and Syntax is compatible with the file used by 'git-cvsimport':
'git-cvsimport':
------------------------------------------------------------------------ ------------------------------------------------------------------------
loginname = Joe User <user@example.com> loginname = Joe User <user@example.com>