[Kde-scm-interest] Meeting minutes

Thiago Macieira thiago at kde.org
Tue Nov 17 08:45:02 CET 2009


Em Segunda-feira 16. Novembro 2009, às 11.12.16, Cornelius Schumacher 
escreveu:
> On Monday 16 November 2009 09:28:31 Simon Hausmann wrote:
> > Therefore I recommend one repository per application, in some cases
> > application + library (say konqueror + libkonq in one repository).
> 
> I see your points and they reflect my experience as well. I have one
>  question, though: With very granular repositories, how is moving code
>  between repositories handled? How can we prevent loss of the history when
>  this is done. We know that this happens quite often, so we need to have a
>  good answer to this.

Then we don't move the code, we move the repository.

That is, an application/library that is born in playground is given its own 
repository. Then it moves to kdereview by simple changing of the KDE 
structure: the repository stays exactly where it is. When it moves to 
extragear, it's another structure change. If we split the main modules, the 
same remains true for it as well: when moving to the main modules, it's a 
simple structure change.

Now, if you talk about moving code from one repository to another, like a 
class from an app that gets moved to one of the kdelibs libraries, or across 
one of those libraries (KApplication from kdecore to kdeui for example), then 
there's no history kept.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20091117/738bb628/attachment.sig 


More information about the Kde-scm-interest mailing list