On Sep 16, 2015, at 10:02 PM, David Mason <dma...@ryerson.ca> wrote: > > On 16 September 2015 at 21:56, Steve Stefanovich <s...@stef.rs> wrote: > Isn't the main annoyance the need to commit two times, one in nested > checkout and one in the 'root' repo, and to try to keep timeline order in > both? > > How do you guys manage that - prevent committing/cloning to root and always > use sub-repos? > > There's only one commit, in the sub-repo, unless I change something in the > root repo, but that's pretty rare for me.
My use of nested repos is similar: the nested one is rarely-modified, so the problem doesn’t affect me. From my reading of the Git book section previously linked, it looks like this is a mostly manual operation in Git, too, though it has optional flags that can make it do nested commits and such. I can see cases where you might *want* it to be manual, as when the submodule is an external dependency, and you want to “pin” your project to a particular version. But in other cases, it would be nice if a commit or update at the root did the same for all submodules, recursively, every time. It would be analogous to the current autosync setting: sometimes you want it, sometimes you don’t. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
