Re: [RFC] Referring to a submodule state recorded in a supermodule from within the submodule

On Wednesday 05 November 2008, Junio C Hamano wrote:

Johan Herland [off-list ref] writes:

quoted

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.

No, they do. I can clone foo directly from bar/baz's server. The problem 
is that I cannot quickly get at which revision of foo is used by 
bar/baz without tedious cloning and interacting with the superrepos.

I basically want to quickly answer questions like "What are the 
differences between bar's foo and baz's foo (and my own foo)?"


...Johan

-- 
Johan Herland, [off-list ref]
www.herland.net