Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes that are relevant (at least as I understand it). Is there anyway to make this process quicker?

I found this link: http://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repositoryhttps://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes that are relevant (at least as I understand it). Is there anyway to make this process quicker?

I found this link: http://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes that are relevant (at least as I understand it). Is there anyway to make this process quicker?

I found this link: https://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

deleted 326 characters in body
Source Link
jb510
  • 1.2k
  • 16
  • 23

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes thethat are relevant (at least as I understand it). Is there anyway to optimize this or cache things so as to make cloning subsequent plugins from the same svn repo faster?

Probably doesn't matter but I'm using Git Tower as my primary git client, but I'm not at all opposed to command line solutions to this.

Also wondering if anyone has setup an automated clone of the plugin repo on GitHub as has been done with core process quicker?

I found this link: http://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes the are relevant (at least as I understand it). Is there anyway to optimize this or cache things so as to make cloning subsequent plugins from the same svn repo faster?

Probably doesn't matter but I'm using Git Tower as my primary git client, but I'm not at all opposed to command line solutions to this.

Also wondering if anyone has setup an automated clone of the plugin repo on GitHub as has been done with core?

I found this link: http://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes that are relevant (at least as I understand it). Is there anyway to make this process quicker?

I found this link: http://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

Tweeted twitter.com/#!/StackWordPress/status/140978963982979072
added 271 characters in body
Source Link
jb510
  • 1.2k
  • 16
  • 23

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes the are relevant (at least as I understand it). Is there anyway to optimize this or cache things so as to make cloning subsequent plugins from the same svn repo faster?

Probably doesn't matter but I'm using Git Tower as my primary git client, but I'm not at all opposed to command line solutions to this.

Also wondering if anyone has setup an automated clone of the plugin repo on GitHub as has been done with core?

I found this link: http://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes the are relevant (at least as I understand it). Is there anyway to optimize this or cache things so as to make cloning subsequent plugins from the same svn repo faster?

Probably doesn't matter but I'm using Git Tower as my primary git client, but I'm not at all opposed to command line solutions to this.

Also wondering if anyone has setup an automated clone of the plugin repo on GitHub as has been done with core?

When cloning a SVN repo with git-svn it searches laboriously through every revision for changes the are relevant (at least as I understand it). Is there anyway to optimize this or cache things so as to make cloning subsequent plugins from the same svn repo faster?

Probably doesn't matter but I'm using Git Tower as my primary git client, but I'm not at all opposed to command line solutions to this.

Also wondering if anyone has setup an automated clone of the plugin repo on GitHub as has been done with core?

I found this link: http://stackoverflow.com/questions/747075/how-to-git-svn-clone-the-last-n-revisions-from-a-subversion-repository that suggests it is possible to limit the number of revisions, just need to figure out how far back to go and how to find that number

added 114 characters in body
Source Link
jb510
  • 1.2k
  • 16
  • 23
Loading
Source Link
jb510
  • 1.2k
  • 16
  • 23
Loading