all of those you listed, when you look at the fork path, can be traced to the real root, but thats the point to git, the main might have a bug, and becasue you can fork, and give pull-requests, until main is fixed, yours could be counted as the "real" one
On Fri, Aug 12, 2011 at 11:26 AM, Derick Rethans <der...@php.net> wrote: > On Sun, 7 Aug 2011, Stas Malyshev wrote: > > > On 8/7/11 2:13 PM, Richard Quadling wrote: > > > > You can build single-source workflows around DCVS too. The fact that > > everybody is keeping the copy of the history doesn't mean there can't > > be one "main" repository. The point of DCVS is not as much in doing > > different things from what we're doing now as doing roughly the same > > things in a better way - more efficiently. > > > > > The main thing I'm worried about is if feature X splits the core devs > > > so much that there are 2 competing repos, both with a significant > > > number of core devs supporting each repo, how do I choose which is > > > which? If my abilities include being able to code at the core level, > > > which should I support? Both? All 3, 4 or 10 different forks? > > > > This can happen right now - take the code, put it on any of the hosting > > facilities and declare yourself the new king of PHP. > > But you can't call it PHP anymore due to the license, where as with a > DCVS with people having forks on publically accessible repositories, > everybody is basically violating the license. > > I share Richard's concerns about finding out "what is the real one"/best > one/latest one. > > Most recently I found that out with two related PHP projects: > > https://github.com/preinheimer/xhprof vs > https://github.com/facebook/xhprof > > and: > https://github.com/corretge/xdebug-trace-gui or > https://github.com/beberlei/xdebug-trace-gui or > http://www.rdlt.com/xdebug-trace-file-parser.html > > regards, > Derick > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
