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

List:       kde-core-devel
Subject:    Re: clarification on git, central repositories and commit access lists
From:       "Boyd Stephen Smith Jr." <bss03 () volumehost ! net>
Date:       2007-08-20 13:38:23
Message-ID: 200708200838.23675.bss03 () volumehost ! net
[Download RAW message or body]


On Monday 20 August 2007, Thiago Macieira <thiago@kde.org> wrote about 'Re: 
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 
show up as three different commits on the server side (at no time will the 
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 
used.

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

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

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