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

List:       kde-core-devel
Subject:    Re: Version mismatch when building trunk
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2009-10-16 15:32:16
Message-ID: 200910161732.21648.kevin.krammer () gmx ! at
[Download RAW message or body]


On Friday, 2009-10-16, 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.

Ok, thanks. Clone it is then.
As a bonus it removes the need for make confclean :)

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

["signature.asc" (application/pgp-signature)]

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