{"thread":{"id":"14750","subject":"[PATCH v2] Documentation: Remove mentions of git-svnimport.","startedAt":"2008-07-30T01:16:01Z","lastAt":"2008-07-30T01:16:01Z","messageCount":1,"participants":["Brian Gernhardt"],"isPatch":true,"patchVersion":2,"patchTotal":null},"messages":[{"id":"85556","messageId":"20080730011601.GA944@Hermes","threadId":"14750","inReplyTo":null,"subject":"[PATCH v2] Documentation: Remove mentions of git-svnimport.","fromName":"Brian Gernhardt","fromEmail":"benji@silverinsanity.com","sentAt":"2008-07-30T01:16:01Z","receivedAt":"2008-07-30T01:16:01Z","isPatch":true,"sender":{"key":"benji@silverinsanity.com","avatar":"https://gravatar.com/avatar/e06c101dbc25c68114d859b4a9ec7cf8a2c52fd2b0270ef0eac0e2e63ff22311?d=mp&s=160"},"body":"git-svnimport is no longer supported, so don't mention it in the\ndocumentation.  This also updates the description, removing the\nhistorical discussion, since it mostly dealt with how it differed from\nsvnimport.  The new description gives some starting points into the\nrest of the documentation.\n\nNoticed by Jurko Gospodnetić <jurko.gospodnetic@docte.hr>\n\nSigned-off-by: Brian Gernhardt <benji@silverinsanity.com>\n---\n\n Replaces the remaining comparison to git-svnimport with pointers\n to the rest of the documentation.\n\n Documentation/git-svn.txt |   26 ++++++++++++--------------\n 1 files changed, 12 insertions(+), 14 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex e7c0f1c..f230125 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -12,18 +12,18 @@ SYNOPSIS\n DESCRIPTION\n -----------\n 'git-svn' is a simple conduit for changesets between Subversion and git.\n-It is not to be confused with linkgit:git-svnimport[1], which is\n-read-only.\n+It provides a bidirectional flow of changes between a Subversion and a git\n+respository.\n \n-'git-svn' was originally designed for an individual developer who wants a\n-bidirectional flow of changesets between a single branch in Subversion\n-and an arbitrary number of branches in git.  Since its inception,\n-'git-svn' has gained the ability to track multiple branches in a manner\n-similar to 'git-svnimport'.\n+'git-svn' can track a single Subversion branch simply by using a\n+URL to the branch, follow branches laid out in the Subversion recommended\n+method (trunk, branches, tags directories) with the --stdlayout option, or\n+follow branches in any layout with the -T/-t/-b options (see options to\n+'init' below, and also the 'clone' command).\n \n-'git-svn' is especially useful when it comes to tracking repositories\n-not organized in the way Subversion developers recommend (trunk,\n-branches, tags directories).\n+Once tracking a Subversion branch (with any of the above methods), the git\n+repository can be updated from Subversion by the 'fetch' command and\n+Subversion updated from git by the 'dcommit' command.\n \n COMMANDS\n --------\n@@ -218,8 +218,7 @@ Any other arguments are passed directly to 'git-log'\n \n 'commit-diff'::\n \tCommits the diff of two tree-ish arguments from the\n-\tcommand-line.  This command is intended for interoperability with\n-\t'git-svnimport' and does not rely on being inside an `git-svn\n+\tcommand-line.  This command does not rely on being inside an `git-svn\n \tinit`-ed repository.  This command takes three arguments, (a) the\n \toriginal tree to diff against, (b) the new tree result, (c) the\n \tURL of the target Subversion repository.  The final argument\n@@ -317,8 +316,7 @@ config key: svn.findcopiesharder\n -A<filename>::\n --authors-file=<filename>::\n \n-Syntax is compatible with the files used by 'git-svnimport' and\n-'git-cvsimport':\n+Syntax is compatible with the file used by 'git-cvsimport':\n \n ------------------------------------------------------------------------\n \tloginname = Joe User <user@example.com>\n-- \n1.6.0.rc1.154.ge3fc\n"}]}