[cfe-dev] [LLVMdev] GIT mirrors

Lenny Maiorani lenny at Colorado.EDU
Wed Mar 30 13:28:00 PDT 2011


On 03/30/2011 01:48 PM, Konstantin Tokarev wrote:
>
> 30.03.2011, 22:45, "Lenny Maiorani"<lenny at Colorado.EDU>:
>> On 03/14/2011 01:07 PM, Justin Holewinski wrote:
>>
>>>   Alright, figured it out.  Thanks to Tobias for the git insight!
>>>
>>>   The previous way I was using the git-svn bridge was to pull from
>>>   refs/remotes/git-svn (learned from an older post on the list).
>>>    However, git-svn does not appear to be a valid, up-to-date ref
>>>   anymore.  It only pulls history through March 10, which I assume is
>>>   the around the time the layout change occurred.  The fix is to have
>>>   git-svn read from refs/remotes/origin/master instead of relying on
>>>   refs/remotes/git-svn.  Now it works great!
>>>
>>>   So, instead of:
>>>   git config --add remote.origin.fetch
>>>   '+refs/remotes/git-svn:refs/remotes/git-svn'
>>>
>>>   I needed:
>>>   git config svn-remote.svn.fetch ":refs/remotes/origin/master"
>> Maybe my git-fu isn't up to par... Ok, so I am trying this:
>>
>>       git clone http://llvm.org/git/llvm.git
>>       cd llvm.git
>>       git config svn-remote.svn.fetch ":refs/remotes/origin/master"
>>       git fetch
>>       git svn init https://llvm.org/svn/llvm-project/llvm/trunk
>>       git svn rebase -l
>>
>> The last command hangs for a long time, sucking up a lot of CPU cycles
>> then spits out this message:
>>
>>       Unable to determine upstream SVN information from working tree history
>>
>> Anybody know what the problem is?
>
> Do you really need to bother with git-svn when you have valid git mirror?
>
>
Oh, if it is a valid git mirror then I do not. A month or so ago, it did 
need that, but I guess since it has been changed over I don't anymore. 
Thanks for pointing out the obvious.

-Lenny




More information about the cfe-dev mailing list