llvm dev - Mar 2010 - [LLVMdev] [repository] Make LLVM repository Git-clonable

On Mar 28, 2010, at 10:35 AM, Jon wrote:
>> A good solution, surely, would be to anoint a single official
>> Git/Mercurial mirror, and announce it in the same page as the SVN
>> checkout instructions?
> 
> MRI Ruby interpreter development did that and it seems to working fine.  Of
interest is their handling of branches and tags as discussed by Vladimir and
Eric in this post:
FWIW, One aim of the new llvm.org server is for it to host an 'official'
live git mirror.

-Chris

On 03/28/2010 09:54 PM, Chris Lattner wrote:
> On Mar 28, 2010, at 10:35 AM, Jon wrote:
> 
>>> A good solution, surely, would be to anoint a single official
>>> Git/Mercurial mirror, and announce it in the same page as the SVN
>>> checkout instructions?
>> MRI Ruby interpreter development did that and it seems to working fine.
Of interest is their handling of branches and tags as discussed by Vladimir and
Eric in this post:
> 
> FWIW, One aim of the new llvm.org server is for it to host an
'official' live git mirror.
That'd be lovely, any estimate on when it will be done?

Will it include full history, and all branches/tags, and use svn
post-commit hook to update git repo?
Having at least trunk and the release branches would be great too.

(importing the full history can be done the fastest by running git-svn
locally on the llvm.org server, using file:// paths.)

Best regards,
--Edwin

2010/3/31 Török Edwin <edwintorok at gmail.com>:
> On 03/28/2010 09:54 PM, Chris Lattner wrote:
>> On Mar 28, 2010, at 10:35 AM, Jon wrote:
>>
>>>> A good solution, surely, would be to anoint a single official
>>>> Git/Mercurial mirror, and announce it in the same page as the
SVN
>>>> checkout instructions?
>>> MRI Ruby interpreter development did that and it seems to working
fine.  Of interest is their handling of branches and tags as discussed by
Vladimir and Eric in this post:
>>
>> FWIW, One aim of the new llvm.org server is for it to host an
'official' live git mirror.
>
> That'd be lovely, any estimate on when it will be done?
>
> Will it include full history, and all branches/tags, and use svn
> post-commit hook to update git repo?
> Having at least trunk and the release branches would be great too.
>
> (importing the full history can be done the fastest by running git-svn
> locally on the llvm.org server, using file:// paths.)
>
Looking forward to this myself. Several other projects have ended up
making a full transition to Git -- GNOME (from Subversion) and
Dragonfly BSD (from CVS) spring to mind. If you can migrate even from
CVS, doing it from SVN ought to be relatively trivial -- git-svn is
not bulletproof (at least in the past) but it can resume an
interrupted fetch job.

Best regards,

-- 
Michel Alexandre Salim