Re: dependable submodules

[Daniel <daniel@netwalk.org>]

On Sat, Mar 19, 2011 at 9:27 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Daniel <daniel@netwalk.org> writes:
>
>> IOW, I may have
>>
>>     myrepo/somefile.txt
>>     myrepo/another_project/.git/...
>>     myrepo/another_project/another_project_file.txt
>>
>> and I'd like to, when I clone repo, to be able to get all files from
>> repo independently of the remote repo's existence.
>
> Cloned repositories from your repository can say where they get from
> "another_project" embedded in it in .git/config of the clone of the
> superproject. The supermodule may have .gitmodules that points at github
> or whereever your original upstream repository resided, but that is
> supposed to be used to only give you the default.
>
> When "another_project" you borrowed really dies and becomes useless for
> anybody, you may update its entry in .gitmodules of the superproject to
> point at the public repository that inherited that submodule project.
> The project might be simply abandoned, in which case you end up being
> that inheritor.
>

So would it be correct to say that even though those files are
remotely fetched on a clone of the repository, they are actually
revisioned and stored in the super project?

This would have to be true for me to be able to still be able to
access those files in which case the project was abandoned (or if I
lacked internet access).

-d


-- 
"America was founded by men who understood that the threat of domestic
tyranny is as great as any threat from abroad. If we want to be worthy
of their legacy, we must resist the rush toward ever-increasing state
control of our society. Otherwise, our own government will become a
greater threat to our freedoms than any foreign terrorist."
 - Ron Paul, Texas Straight Talk, May 31, 2004