[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-19 7:54:34
Message-ID: 200910190954.35154.thiago () kde ! org
[Download RAW message or body]


Em Segunda-feira 19 Outubro 2009, às 09:07:27, você escreveu:
> Thiago Macieira schrieb:
> > The branch switching is necessary in the workflow I created because I'm
> > treating kde-qt branches as patch queues. Each time I create a new
> > branch, I reapply all the previous patches from KDE, while local changes,
> > like backports from Qt itself, are lost. We start anew.
> 
> You could create a branch latest-stable that merges 4.6-stable etc. such
> that the merge always takes the content of the merged-in branch. Then
> people need just track lastest-stable, and they will be fast-forwarded by
> the next git pull.

Hi

Yes, I'm thinking of doing that and calling it very simply "master" (to create 
confusion).

But like I said, it will be a branch that will have forever a delta to Qt's 
own branches.

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