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

Hi,

As a Linux package maintainer I tend to follow LLVM mostly towards the
end of each release cycle; nevertheless, I sometimes need to keep
track of multiple LLVM branches at the same time.

It would be great if I could use Git's SVN to clone the repository
once, and then have the full version history available locally in a
compact format. As a bonus, this will reduce the load on the server
too.

There are LLVM Git mirrors (there's one on GitHub, and I used to have
a personal clone too) but they all track only the trunk directory, for
the following reason:
> git svn clone --no-minimize-url -s http://llvm.org/svn/llvm-project/llvm
llvm
Initialized empty Git repository in /home/inf2/i2staff/salim/checkout/llvm/.git/
RA layer request failed: Server sent unexpected return value (403
Forbidden) in response to REPORT request for
'/svn/llvm-project/!svn/vcc/default' at /usr/lib/git/git-svn line 5047

Any idea if this could be rectified?

Thanks,

-- 
Michel Alexandre Salim
Fedora Project

On Sat Mar 27 21:38:52 +0100 2010, Michel Alexandre Salim
wrote:
> There are LLVM Git mirrors (there's one on GitHub, and I used to have
> a personal clone too) but they all track only the trunk directory
The Git mirror I maintain at http://github.com/earl/llvm-mirror has
releases branches (and tags), currently going back to the 2.0 release.
Once 2.7 is released, I'll add the according branch and tag.

-- 
Regards,
Andreas

Hi Andreas,

On Sat, Mar 27, 2010 at 10:08 PM, Andreas Bolka <andreas.bolka at gmx.net>
wrote:
> On Sat Mar 27 21:38:52 +0100 2010, Michel Alexandre Salim wrote:
>> There are LLVM Git mirrors (there's one on GitHub, and I used to
have
>> a personal clone too) but they all track only the trunk directory
>
> The Git mirror I maintain at http://github.com/earl/llvm-mirror has
> releases branches (and tags), currently going back to the 2.0 release.
> Once 2.7 is released, I'll add the according branch and tag.
>
Aha, thanks! 2.7 has been branched in SVN, though, so I'm guessing at
the moment SVN trunk (and your master branch) is not what will end up
as LLVM 2.7 ?

Do you need SVN commit access to be able to make the Git mirror, or is
a purely read-only access sufficient? I'd appreciate it if you could
demonstrate how it's done.

Thanks,

-- 
Michel Alexandre Salim

On Sat, Mar 27, 2010 at 4:38 PM, Michel Alexandre Salim
<michael.silvanus at gmail.com> wrote:
>> git svn clone --no-minimize-url -s
http://llvm.org/svn/llvm-project/llvm llvm
> Initialized empty Git repository in
/home/inf2/i2staff/salim/checkout/llvm/.git/
> RA layer request failed: Server sent unexpected return value (403
> Forbidden) in response to REPORT request for
> '/svn/llvm-project/!svn/vcc/default' at /usr/lib/git/git-svn line
5047
>
> Any idea if this could be rectified?
Several months ago it was determined that people scraping SVN history
into their DVCS clones were hosing the server, so some attempt was
made to forbid that, which I think you are running into.

Reid

On Sun, Mar 28, 2010 at 7:05 AM, Reid Kleckner <rnk at mit.edu>
wrote:
> On Sat, Mar 27, 2010 at 4:38 PM, Michel Alexandre Salim
> <michael.silvanus at gmail.com> wrote:
>>> git svn clone --no-minimize-url -s
http://llvm.org/svn/llvm-project/llvm llvm
>> Initialized empty Git repository in
/home/inf2/i2staff/salim/checkout/llvm/.git/
>> RA layer request failed: Server sent unexpected return value (403
>> Forbidden) in response to REPORT request for
>> '/svn/llvm-project/!svn/vcc/default' at /usr/lib/git/git-svn
line 5047
>>
>> Any idea if this could be rectified?
>
> Several months ago it was determined that people scraping SVN history
> into their DVCS clones were hosing the server, so some attempt was
> made to forbid that, which I think you are running into.
>
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?

Thanks,

-- 
Michel Alexandre Salim