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

List:       kde-core-devel
Subject:    Re: Version mismatch when building trunk
From:       David Jarvie <djarvie () kde ! org>
Date:       2009-10-18 19:16:57
Message-ID: 200910182016.57941.djarvie () kde ! org
[Download RAW message or body]

On Friday 16 Oct 2009 09:01:39 Thiago Macieira wrote:
> Em Sexta-feira 16. Outubro 2009, ās 08.50.19, Kevin Krammer escreveu:
> > On Friday, 2009-10-16, Thiago Macieira wrote:
> > > Em Quinta-feira 15. Outubro 2009, ās 23.53.18, Chani escreveu:
> > > > so if there *is* a way for people to set up their git repository so
> > > > that it automagically updates to the latest recommended qt with just a
> > > > 'git pull' or whatever, can we have instructions for that please? :)
> > > 
> > > There is a way, provided you never have commits of your own on top.
> > > 
> > > git fetch origin HEAD
> > > git reset --hard FETCH_HEAD
> > 
> > So if I do that now or right after a clone, do I have to repeat it before
> > every update or does this make the KDE branch permanently work the way it
> > is intended?
> 
> When you clone, you get the branch that HEAD points to.
> 
> But then you are at that branch. If HEAD points somewhere else, you won't 
> know. You need to run these commands above for every update.

I followed the above instructions, but the branch wasn't renamed. To avoid later \
confusion, a branch rename command is also needed, but how can you know what branch \
HEAD now points to?

-- 
David Jarvie.
KDE developer.
KAlarm author and maintainer.
http://www.astrojar.org.uk/kalarm


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