--nextPart2666032.u3AMfA6mOx
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Em Segunda-feira 19 Outubro 2009, =C3=A0s 09:07:27, voc=C3=AA 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 change=
s,
> > like backports from Qt itself, are lost. We start anew.
>=20
> 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 cre=
ate=20
confusion).

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

=2D-=20
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

--nextPart2666032.u3AMfA6mOx
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBK3Bs7M/XwBW70U1gRAmPEAJwKd/drxvYZnBfOacvcni5rN2Z/PwCgyHJT
DbAr/JuOr6czij/dZRyIqrs=
=tj79
-----END PGP SIGNATURE-----

--nextPart2666032.u3AMfA6mOx--