{"thread":{"id":"16011","subject":"Start git svn clone at specific revision for cloning subprojects in large svn repositories?","startedAt":"2008-10-22T15:00:24Z","lastAt":"2008-10-22T15:08:43Z","messageCount":3,"participants":["Jeff Kowalczyk","Jacob Helwig","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"93692","messageId":"pan.2008.10.22.15.00.21.403423@yahoo.com","threadId":"16011","inReplyTo":null,"subject":"Start git svn clone at specific revision for cloning subprojects in large svn repositories?","fromName":"Jeff Kowalczyk","fromEmail":"jtk@yahoo.com","sentAt":"2008-10-22T15:00:24Z","receivedAt":"2008-10-22T15:00:24Z","isPatch":false,"sender":{"key":"jtk@yahoo.com","avatar":null},"body":"I would like to git svn clone subprojects from a large community\nsubversion repository (plone collective).\n\nThe repository is currently at 74K commits, but subprojects of interest\nare typically much more recent, and their initial import revision is known.\n\nI would like to avoid a) unnecessary traffic to the svn server and b)\nthe very long delay in git svn cloning these subprojects.\n\nIs there a way to specfiy a starting revision to git svn clone?\n\nThanks.\n \n"},{"id":"93693","messageId":"8c9a060810220807q14ede199u205d35223f8a4710@mail.gmail.com","threadId":"16011","inReplyTo":"pan.2008.10.22.15.00.21.403423@yahoo.com","subject":"Re: Start git svn clone at specific revision for cloning subprojects in large svn repositories?","fromName":"Jacob Helwig","fromEmail":"jacob.helwig@gmail.com","sentAt":"2008-10-22T15:07:47Z","receivedAt":"2008-10-22T15:07:47Z","isPatch":false,"sender":{"key":"jacob.helwig@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14557?v=4"},"body":"On Wed, Oct 22, 2008 at 08:00, Jeff Kowalczyk <jtk@yahoo.com> wrote:\n> I would like to git svn clone subprojects from a large community\n> subversion repository (plone collective).\n>\n> The repository is currently at 74K commits, but subprojects of interest\n> are typically much more recent, and their initial import revision is known.\n>\n> I would like to avoid a) unnecessary traffic to the svn server and b)\n> the very long delay in git svn cloning these subprojects.\n>\n> Is there a way to specfiy a starting revision to git svn clone?\n>\n> Thanks.\n>\n>\n>\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n\nTry git svn init, then git svn fetch --revision <revision#>:HEAD.\nThis is what I use for some of our larger projects at work.\n"},{"id":"93694","messageId":"48FF41FB.4080403@drmicha.warpmail.net","threadId":"16011","inReplyTo":"pan.2008.10.22.15.00.21.403423@yahoo.com","subject":"Re: Start git svn clone at specific revision for cloning subprojects in large svn repositories?","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2008-10-22T15:08:43Z","receivedAt":"2008-10-22T15:08:43Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Jeff Kowalczyk venit, vidit, dixit 10/22/08 17:00:\n> I would like to git svn clone subprojects from a large community\n> subversion repository (plone collective).\n> \n> The repository is currently at 74K commits, but subprojects of interest\n> are typically much more recent, and their initial import revision is known.\n> \n> I would like to avoid a) unnecessary traffic to the svn server and b)\n> the very long delay in git svn cloning these subprojects.\n> \n> Is there a way to specfiy a starting revision to git svn clone?\n\nYour friendly man page provider says:\n\n       -r <ARG>, --revision <ARG>\n           Used with the fetch command.\n\n           This allows revision ranges for partial/cauterized history to\nbe supported. $NUMBER, $NUMBER1:$NUMBER2 (numeric\n           ranges), $NUMBER:HEAD, and BASE:$NUMBER are all supported.\n\n           This can allow you to make partial mirrors when running\nfetch; but is generally not recommended because history\n           will be skipped and lost.\n\nUsage of \"Scroll Down\" is strongly advised when viewing git help svn ;)\n\nMichael\n\nP.S.: It works nicely, don't mind the warning in the man page if you\nknow the start rev for sure.\n"}]}