[Kde-scm-interest] Meeting minutes

[Oswald Buddenhagen]

On Thu, Nov 12, 2009 at 11:25:12PM +0100, Thomas Zander wrote:
> On Thursday 12. November 2009 23.01.42 Oswald Buddenhagen wrote:
> > > It is possible to move an independent git repo into another. Its
> > > not trivial, not something you want to do everyday, but it is
> > > possible.
> >
> > i said *clean*.
> 
> Yes you did, why do you repeat it?
> 
because the above proposal is in no way clean. the imported history is
completely rebased on top of the target module. that way it is
impossible to create an even remotely consistent checkout of a past
state where the two modules were still separate.

> > > But actually this is one of the reasons we want to keep the kde
> > > modules whole. It becomes trivial to move stuff around within
> > > kdebase for example.
> >
> > moving stuff within a module is probably the more seldom case.
> > usually, stuff gets moved between modules (typical application
> > "introduction cycle", random app code moving to kdelibs).
> 
> An application can be created in a new repo and the staging areas we
> used before will become less of an issue after moving to git.  Not
> really a big need to have a review area etc if the app is one repo.
>
the need to have the stages doesn't magically go away. the handling will
just change somewhat.

> If it gets ok-ed for inclusion in one of the big modules its entirely 
> possible to move it in there without loss of history.
> 
yeah, right ...

> But all this is not really an issue for the conversion, this is an
> issue to discuss after we moved to Git and it likely not be decided on
> this list.
>
this is most certainly wrong. once stuff is converted, there is no sane
way to rearrange stuff. sane being defined as a) not creating an
incredible bloat and b) not distorting the history (including externally
referenced sha1s).

i'm also still missing a single argument *for* big repositories which is
not easily refuted.