[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:       "koos vriezen" <koos.vriezen () gmail ! com>
Date:       2007-08-20 7:11:09
Message-ID: d4e708d60708200011p6c7d3d34x1dada011208b963b () mail ! gmail ! com
[Download RAW message or body]

2007/8/20, Guillaume Laurent <glaurent@telegraph-road.org>:
> 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.

How does this work with SVN? I can't see at my project that is depends
on kde-3.1.1 or later. How can I mark my files to do that?

Br.
Koos
[prev in list] [next in list] [prev in thread] [next in thread]