Proposal for branching policy towards KF5

[Ben Cooksley]

On Sun, Jul 21, 2013 at 9:54 PM, Thomas Lübking
<thomas.luebking at gmail.com> wrote:
> On Sonntag, 21. Juli 2013 11:15:29 CEST, Ben Cooksley wrote:
>>
>> On Sun, Jul 21, 2013 at 9:13 PM, Thomas Lübking
>> <thomas.luebking at gmail.com> wrote:
>>>
>>> On Sonntag, 21. Juli 2013 05:04:10 CEST, Michael Pyne wrote:
>>>>
>>>> On Fri, July 19, 2013 00:21:21 David Faure wrote: ...
>>>
>>>
>>>
>>>
>>> git symbolic-ref refs/heads/NEXT refs/heads/master
>>> or for workspace/libs
>>> git symbolic-ref refs/heads/NEXT refs/heads/KDE/4.11
>>>
>>> eventually also
>>> git symbolic-ref refs/heads/CURRENT refs/heads/KDE/4.11
>>>
>>> and then at some point
>>> git symbolic-ref --delete refs/heads/CURRENT
>>> git symbolic-ref refs/heads/CURRENT refs/heads/KDE/4.12
>>
>>
>> It would appear that "git remote update" does not handle symbolic refs
>> at all (at least it does not handle HEAD)
>
>
> Tried recently?
> HEAD used to be a symbolic link rather than a symbolic-ref; Technically, the
> symbolic ref is ("now") just a ref that instead

Yes, I ran into this problem recently because a couple of Qt 5 modules
changed their HEAD. This broke our mirrored copies of Qt.

>
> $ cat .git/refs/heads/master
> 65dd83dfb5593eebaec44b71925c15cee5955e9a
>
> contains
>
> $ cat .git/refs/heads/NEXT
> ref: refs/heads/master
>
> Not sure why it would not be passed around like any other ref - but i really
> don't know ;-)

It is passed around on the initial "git clone --mirror" but it is not
subsequently updated unfortunately - unless there is a different
command other than "git remote update -p" to run - If there is I would
definitely like to know about it.

>
> Norm!
> Thomas

Thanks,
Ben