[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] requirements on git itself:
From:       "Patrick Aljord" <patcito () gmail ! com>
Date:       2008-08-16 19:50:38
Message-ID: 6b6419750808161250p285d67bbg18644a9f50948a26 () mail ! gmail ! com
[Download RAW message or body]

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".

Also that way, you don't need to commit a second time to the
supermodule every time you do a commit to a submodule.
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
[prev in list] [next in list] [prev in thread] [next in thread]