clarification on git, central repositories and commit access lists

[Thomas Zander]

On Monday 20 August 2007 09:02:45 Guillaume Laurent wrote:
> On Monday 20 August 2007, Adam Treat wrote:
> > What if I want to make a commit to kdelibs that will require changes
> > in other modules for them to compile.  I will no longer be able to
> > make a single atomic commit with changes to multiple submodules,
> > right?
>
> That was one of my main interrogations about the idea of having several
> repositories as well. Also, how do you handle backtracking ? Do you
> have to maintain a table saying 'version [N1-M1] of kdegraphics need
> version [N2-M2] of kdelibs' ? That pretty much defeats the idea of a
> version control system, unless I'm missing something.

When I type svn update in koffice I can easily end up with a non compiling 
version due to kdelibs having some changes because svn doesn't have 
atomic commits.  It doesn't auto-update the same thing in kdelibs.
This means that the problem you are seeing is a problem we deal with every 
(mon)day. Its not new and its never been solved before.

So I think the statement that it defeats the idea of versioning is a bit 
over the top :)

-- 
Thomas Zander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070820/dc4a95dd/attachment.sig>