Version mismatch when building trunk

Kevin Krammer kevin.krammer at gmx.at
Fri Oct 16 16:32:16 BST 2009


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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20091016/7465fa7f/attachment.sig>


More information about the kde-core-devel mailing list