--nextPart3322468.eUZviHoKy6
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 20 August 2007, Thiago Macieira <thiago@kde.org> wrote about 'Re:=
=20
clarification on git, central repositories and commit access lists':
> No, I want this:
>
> kdelibs# work...
> kdelibs# commit -m "New API"
> kdelibs# work...
> kdelibs# commit -m "Adapt kdelibs to new API"
> kdelibs# cd ../kdegames
> kdegames# work...
> kdegames# commit -m "Adapt kdegames to new API"
> kdegames# cd ..
> KDE# push all changes

One big git tree would do that, although since you did 3 commits it will=20
show up as three different commits on the server side (at no time will the=
=20
server's HEAD be one of the first two commits, though).

Not sure how to get similar behavior if I'm separate git repositories are=20
used.

=2D-=20
Boyd Stephen Smith Jr.                     ,=3D ,-_-. =3D.=20
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-'=20
http://iguanasuicide.org/                      \_/    =20

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.6 (GNU/Linux)

iD8DBQBGyZlP55pqL7G1QFkRAn2vAJ9gvikMkUCqkMAgsWVWUVDfQtssMQCeP/+x
e9mL/TtQiyl09mm3hvGtyzE=
=6aWR
-----END PGP SIGNATURE-----

--nextPart3322468.eUZviHoKy6--