[Kde-scm-interest] Layout of the Git repositories for KDE (proposal #2)

Riccardo Iaconelli riccardo at kde.org
Wed Nov 7 14:11:07 CET 2007

On Monday 05 November 2007 16:42:37 Johannes Sixt wrote:
> Thiago Macieira schrieb:
> > After realising that we don't have to keep the history of the
> > supermodules, I came up with a different idea. Here's it:
> Of course, you need to track the history of supermodules. How else would
> you handle atomic cross-module commits?

By the way, given that most of the development should happen into projects/, 
how are we going to make sure that developers can easily apply cross-module 
changes to the repo in projects?
Take an example:
Someone does a big api change, and does all the porting necessary to all KDE/. 
He does a cross-module commit, with both the api change, and all the 
applications ported to the new stuff.
The maintainer, of, for example, kig, has a projects/kig.git repo, where he 
does most of the work. As the crossmodule commit has been done on the 
kdeedu.git, how can he backport the change to kig easily and apply it to the 
code in projects/, so he can continue to work happily?

GPG key:
When encrypting, please encrypt also for this subkey:
Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平
Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch
Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화

More information about the Kde-scm-interest mailing list