Cron <git-svn at code> $HOME/git-svn-sync

[John Ralls]

On Aug 23, 2013, at 7:04 AM, Derek Atkins <warlord at MIT.EDU> wrote:

> John Ralls <jralls at ceridwen.us> writes:
> 
>> On Aug 22, 2013, at 6:05 AM, Derek Atkins <warlord at MIT.EDU> wrote:
>> 
>>> John Ralls <jralls at ceridwen.us> writes:
>>> 
>>>>> Well, our instructions do specify pulling out -b trunk...  I'm not sure
>>>>> what would happen if you 'git svn init' and push from "master".
>>>> 
>>>> I *think* it would raise an error about not having an svn branch
>>>> corresponding to 'master'. But I'm not going to test it! ;-)
>>> 
>>> I suppose we could test it on a standalone svn/git-svn test setup...
>>> Besides, didn't the github repos already have 'master' setup?  ISTR you
>>> could just to a 'git clone' from github without specifying '-b trunk'
>> 
>> I suppose we could, but I don't have time to set one up right now.
>> 
>> I *thought* that we'd removed master from Github and that since the
>> default branch there is set to trunk
>> that that's what it would send for an unqualified clone, but I could
>> easily be mis-remembering. It does send
>> master now, I tested that Tuesday.
> 
> Even worse, it's now sending two updates every time there's an update to
> the SVN repo.  It wasn't doing this before, so clearly something else
> must be wrong/missing..  The behavior is definitely different now.

I suspect that until the 15th the master branch existed but wasn't an alias.

You could restore that configuration with `git symbolic-ref --delete refs/heads/master; git branch master`,
or you could get rid of master and set HEAD to trunk: `git symbolic-ref --delete refs/heads/master; git symbolic-ref HEAD refs/heads/trunk`.

Regards,
John Ralls