Re: [SVN-MIGRATION] Re: Github

[email protected] (shire) Wed, 25 Feb 2009 15:19:26 -0800
Newsgroups svn.migration
Message-ID <[email protected]>
Johannes Schlüter wrote:
> On Wed, 2009-02-25 at 14:42 -0800, shire wrote:
>> Rasmus Lerdorf wrote:
>>> As Brian said, github gives us a decent Web interface and a really easy
>>> way to make dev work public.  Git without github is a lot less appealing
>>> to me.  At the same time, giving up control of our master code
>>> repository is rather scary.
>> Oh, I forgot an additional point that I should mention, which is that
>> I don't believe we can port directly from CVS to GIT anyways, as the
>> way things have been moved around within CVS it breaks all the
>> CVS-to-GIT import tools.  All the pecl extensions should work, but
>> there's something wrong with PHP/ZendEngine2 I think. (If someone is
>> able to import correctly, please do share!) We'll likely have to
>> import from our SVN port to get to GIT.  I don't think this is a big
>> argument or anything, just something we should probably be aware of.
>
> http://git.chinstrap.eu/php/php-tsrm-ze2.git/
>
> Looks quite good as a start, compiles nicely on all active branches. But
> didn't check all parts of the history.
>

HUh, are you importing this with the git-cvsimport tools?  I had been doing this myself for a while and when we started 5.3 I started noticing differences between GIT and CVS HEAD.  Looks like I emailed David Soria Parra about this and some other bugs (included excerpt below).  Maybe some of these issues have been fixed? (crosses fingers)

David Soria Parra wrote:
> > Hi,
> >
> > I recently noticed your comment on my blog about the problems with the
> > PHP git repository. We know that there are problems with phar, as the
> > php team just copied the ,v files from the pecl repository into the
> > php-src repository, resulting in not synced branched.
> >
> > I'm interested in your parsecvs fix. Is there any repository where I can
> > pull those changes? I realy would like to see the php git import fixed.
> > We than just have to fix the zend_language file



-shire