Re: [SVN-MIGRATION] Argh!
| From: | Jani Taskinen | Date: | Sun, 12 Jul 2009 09:42:47 +0000 |
| Subject: | Re: [SVN-MIGRATION] Argh! | ||
| References: | 1 2 3 4 | Groups: | svn.migration |
| Request: | Send a blank email to svn-migration+get-429@lists.php.net to get a copy of this message | ||
Travis Swicegood kirjoitti:
On Jul 11, 2009, at 12:24 PM, Rasmus Lerdorf wrote:If we had wanted to use git, we would. But we didn't so saying it's the reason not to make things easier is moot.Travis Swicegood wrote:Well, off of the top of my head it becomes much, much harder to do a git svn clone on it. :-)That's actually a *really* bad idea. There are a lot of third-party tools that rely on the standard SVN repository layout that this will break. It would be much easier to write a few simple scripts to handle checkouts of multiple repositories or as Hannes pointed out use svn:externals with a few repositories such as pecl-all might also be a good solution.What sort of 3rd party tools? I'm more worried about our own 1st party tools that are currently completely broken because of this structure.
I believe, though I'm not positive since I don't use them on a regular basis, that most GUIs would be broken as well. Subversion doesn't have a real concept of a branch or a tag. They're all just copies of code, so they use a convention in the file-system to denote what's what. Most 3rd-party apps are going to rely on it to show things like branches and tags and whatnot.WHAT 3rd-party apps? Without proof this point is also moot. --Jani