On Wed, Feb 5, 2014 at 10:24 PM, christ...@surlykke.dk
<christ...@surlykke.dk> wrote:
> Which is confusing. There should not be anything with a freshly cloned
> project. The problem is, AFAICT, that when you do a commit & push in a
> subrepo, you have to commit and push in the master repo as well, to make the
> master repo point to the new commit in the subrepo. Right now the master
> repo on github points to old commits in some of the subrepos.
Yes, for the main repo to point to a new commit in an submodule, a new
commit has to be made in the main repo.
But every single commit in the submodules should me committed in the
main one. For example one commit in one submodule could brake
something in another submodule.
The main repo should contain commits that are know to work well.
> Not a huge problem, easy to fix, but it shows that Git submodule is not
> really being used as it should. IMHO we might just as well have a bunch of
> unrelated git repos, and a script to clone them all. But I agree with Petr
> that one repo is strongly preferable.
We are not using submodules the way they are meant to be used.
But I think that having the main repo with commits that are known to
work is a good thing.... but we have to use it the "right" way.
>> However, as the project grows, we'll need to split them someday, and it's
>> easier to do if we do it earlier.
>> I admitted that sometimes I missed the one-repo setup when git submodule
>> does not work as well as expected. :-(
>> Do you have other ideas?
I think that the submodules approach is a good one.
We should learn on how to take advantage of it.
To get the latests commits in the submodules master branches, without
a detached head, we can use:
git submodule update --remote --rebase
--
Luís Pereira
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
