{"thread":{"id":"14749","subject":"[PATCH] Documentation: Remove mentions of git-svnimport.","startedAt":"2008-07-30T00:38:19Z","lastAt":"2008-07-30T00:57:51Z","messageCount":3,"participants":["Brian Gernhardt","Pieter de Bie"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"85549","messageId":"1217378299-733-1-git-send-email-benji@silverinsanity.com","threadId":"14749","inReplyTo":null,"subject":"[PATCH] Documentation: Remove mentions of git-svnimport.","fromName":"Brian Gernhardt","fromEmail":"benji@silverinsanity.com","sentAt":"2008-07-30T00:38:19Z","receivedAt":"2008-07-30T00:38:19Z","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.\n\nNoticed by Jurko Gospodnetić <jurko.gospodnetic@docte.hr>\n\nSigned-off-by: Brian Gernhardt <benji@silverinsanity.com>\n---\n Documentation/git-svn.txt |   22 ++++++----------------\n 1 files changed, 6 insertions(+), 16 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex e7c0f1c..4d82a08 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -12,18 +12,10 @@ 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-\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-\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+It provides a bidirectional flow of changes between a Subversion and a git\n+respository.  'git-svn' is especially useful when it comes to tracking\n+repositories not organized in the way Subversion developers recommend\n+(trunk, branches, tags directories).\n \n COMMANDS\n --------\n@@ -218,8 +210,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 +308,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"},{"id":"85551","messageId":"F11D5504-5FA1-4FF7-9D53-032D5027EBB9@ai.rug.nl","threadId":"14749","inReplyTo":"1217378299-733-1-git-send-email-benji@silverinsanity.com","subject":"Re: [PATCH] Documentation: Remove mentions of git-svnimport.","fromName":"Pieter de Bie","fromEmail":"pdebie@ai.rug.nl","sentAt":"2008-07-30T00:44:40Z","receivedAt":"2008-07-30T00:44:40Z","isPatch":true,"sender":{"key":"pdebie@ai.rug.nl","avatar":null},"body":"\nOn Jul 30, 2008, at 2:38 AM, Brian Gernhardt wrote:\n\n> +respository.  'git-svn' is especially useful when it comes to  \n> tracking\n> +repositories not organized in the way Subversion developers recommend\n> +(trunk, branches, tags directories).\n\nThis is of course not true. Git svn is especially useful when branches  \n_are_ organized\nthat way, but other configurations are somewhat supported. This  \ncomment still refers\nto the comparison with svnimport.\n"},{"id":"85553","messageId":"79AE3D4A-B8E9-413E-9411-6DED84CA9953@silverinsanity.com","threadId":"14749","inReplyTo":"F11D5504-5FA1-4FF7-9D53-032D5027EBB9@ai.rug.nl","subject":"Re: [PATCH] Documentation: Remove mentions of git-svnimport.","fromName":"Brian Gernhardt","fromEmail":"benji@silverinsanity.com","sentAt":"2008-07-30T00:57:51Z","receivedAt":"2008-07-30T00:57:51Z","isPatch":true,"sender":{"key":"benji@silverinsanity.com","avatar":"https://gravatar.com/avatar/e06c101dbc25c68114d859b4a9ec7cf8a2c52fd2b0270ef0eac0e2e63ff22311?d=mp&s=160"},"body":"\nOn Jul 29, 2008, at 8:44 PM, Pieter de Bie wrote:\n\n> On Jul 30, 2008, at 2:38 AM, Brian Gernhardt wrote:\n>\n>> +respository.  'git-svn' is especially useful when it comes to  \n>> tracking\n>> +repositories not organized in the way Subversion developers  \n>> recommend\n>> +(trunk, branches, tags directories).\n>\n> This is of course not true. Git svn is especially useful when  \n> branches _are_ organized\n> that way, but other configurations are somewhat supported. This  \n> comment still refers\n> to the comparison with svnimport.\n\nThe original statement was in a paragraph by itself, so I assumed it  \nwas a not a comparison.  Reading it again, I can see your point.\n\n~~ Brian\n"}]}