Johan Herland <johan@xxxxxxxxxxx> writes: > I have a stand-alone project, "foo", that I work on myself. The "foo" > project is included as a submodule in two other projects, "bar" > and "baz", that I don't have any direct affiliation with. > > Semi-regularly, I like to keep tabs on bar and baz, to see what versions > of foo they are using, what changes they have made to foo, and if there > are things I could pick up from them, or maybe even things they could > learn from eachother. > > Doing this currently is quite tedious: > 1. Clone/Fetch bar and initialize/update its foo submodule > 2. Clone/Fetch baz and initialize/update its foo submodule If I am reading you right and you are only interested in the part "foo" in these projects, there is something wrong with the setup of "bar" and "baz". The submodule mechanism is designed to bind an independent project on its own as a subdirectory of another project. It seems to me that the problem is that "bar" and "baz" projects do not give direct access to clone "foo" part of them for you or other people. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
