[Digikam-devel] Git migration and submodules

Kåre Särs kare.sars at iki.fi
Tue Dec 21 19:50:20 GMT 2010


Kate and Digikam seems to have similar problems to solve when it comes to the 
git migration.

Below is an informative response to my idea to use submodules like it is 
planned in Digikam.

On Tuesday 21 December 2010 17:55:44 Andreas Pakulat wrote:
> On 21.12.10 15:54:23, Kåre Särs wrote:
> > I have not used git much, but if I'm correctly informed, it is possible
> > to create a 'superproject' that has submodules that point to different
> > git repos.
> > 
> > Would this not solve the problem? Kate and kdelibs could point submodules
> > to the same katepart repo with some added logic in the Kate to figure
> > out if the kpart should be compiled...
> > 
> > I got the idea from the kde-imaging/digikam mailings list where they are
> > discussing the move to Git.
> As Ian said, submodules are anything but easy. In particular one needs
> to be really careful during setting up commits in the parent repository
> and even more careful when working inside a submodule (as usually its at
> a specific revision and not on a branch-head. So comitting will not put
> that commit into any branch).
> We're using submodules at work for one project and its still something
> we want to eliminate in the mid-term as we do mess up history in either
> module from time to time and need to rebase stuff and force push to the
> shared repository.
> Oh, last but not least, the kde-scm list has long acknowledged that
> submodules in git are not up to the task of grouping repositories for
> KDE. Thats one of the main reasons we're now having a software on
> projects.kde.org that allows arbitrary nesting of "projects".

Andreas: Can you give any links or information on the nesting software on 


More information about the Digikam-devel mailing list