--nextPart7619188.qSK3g2hIJv
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

Em S=E1bado 17. Outubro 2009, =E0s 20.20.39, Michael Jansen escreveu:
> On Saturday 17 October 2009 19:57:01 you wrote:
> > Em S=E1bado 17. Outubro 2009, =E0s 19.52.08, Michael Jansen escreveu:
> > > Just a short ... maybe dumb ... question. Is it worth the trouble to
> > > not track all remote branches. I mean instead of
> > >
> > >  bash : 1015 ] $ git config --get-all remote.origin.fetch
> > > +refs/heads/*:refs/remotes/origin/*
> > >
> > > having
> > >
> > > [ bash : 1018 ] $ git config --get-all remote.origin.fetch
> > > +refs/heads/4.6-stable-patched:refs/remotes/origin/4.6-stable-patched
> > >
> > > I know that means i have even more maintenance to do on version
> > > switches.
> > >
> > > The question is if this really saves bandwith? And i don't necessarily
> > > mean only in the context of kdeqt. But for example the real qt
> > > repository.
> >
> > I didn't get the question.
> >
> > Why did you change the fetch settings?
>=20
> Why not? Git supports it. The question was: "Does it save bandwidth?".
>=20
> Especially in the qt repo where more than one branch is under development.
>  But given the way git works i'm not sure it will really save bandwidth.

Ah, sorry. I hadn't got the question.

Yes, it saves bandwidth. It doesn't download the other branches.

But since 4.6 contains all of 4.5, the difference is very small. A hundred=
=20
kilobytes or less (out of 170 MB).
=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

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

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

iD8DBQBK2ikxM/XwBW70U1gRArEwAKDEYsFisb1RH+4uK07jehnRae3PFACglcqV
QiRUwikxQYMvHEFd+ea6/eY=
=LQg6
-----END PGP SIGNATURE-----

--nextPart7619188.qSK3g2hIJv--