[Kde-scm-interest] requirements on git itself: ignore-if-not-present submodules

[Thiago Macieira]

Patrick Aljord wrote:
>Sounds good to me.
>
>Another solution would be to not use supermodule and submodules at all.
>That way every kde repository would be independent and you can clone
>the one you want. If a kdelibs commit depends on a kdebase commit, the
>developer can first commit to kdebase and then mention this commit in
>her/his kdelibs commit like "this kdelibs commit depends on that
>kdebase commit".

That sounds easy for kdelibs-kdebase commits, but how about more complex 
stuff? How about going back in history?

Besides, the submodule link was *invented* to keep track of this kind of 
dependency. So why not use it? We just need this extra feature.

BTW, the same feature would be very welcome in our Qt repository too, but 
for a different reason.

>Also that way, you don't need to commit a second time to the
>supermodule every time you do a commit to a submodule.

You don't have to do that now. You only *need* to commit to the 
supermodule to indicate a dependency. Other commits to the supermodule 
would be nice, but not strictly speaking necessary.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    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: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20080817/0cc70feb/attachment.pgp