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

List:       kde-core-devel
Subject:    Re: Version mismatch when building trunk
From:       Thiago Macieira <thiago () kde ! org>
Date:       2009-10-16 8:01:39
Message-ID: 200910161001.56698.thiago () kde ! org
[Download RAW message or body]


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.

> As I said I don't mind cloning everytime but if this makes updates work I'd
>  it would be silly to waste shared resources like gitorous' bandwidth by
>  doing full copies.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

Qt Developer Days 2009 | Registration Now Open!
Munich, Germany: Oct 12 - 14     San Francisco, California: Nov 2 - 4
      http://qt.nokia.com/qtdevdays2009

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

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