[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Proposal for branching policy towards KF5
From:       Thomas_Lübking <thomas.luebking () gmail ! com>
Date:       2013-07-21 9:54:34
Message-ID: ddca8662-0d61-4b55-afb3-0205d065cd49 () gmail ! com
[Download RAW message or body]

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@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

$ 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 ;-)

Norm!
Thomas


[prev in list] [next in list] [prev in thread] [next in thread]