Re: dependable submodules

From: Daniel <daniel@netwalk.org>
Date: Mar 20, 2011, 16:06 UTC
Message-ID: <AANLkTimA-MKXrYfwE+WDOaPd7H1P6vvtcHTC6ODO5kAd@mail.gmail.com>
In-Reply-To: <4D85F4E1.1020607@web.de>

On Sun, Mar 20, 2011 at 5:36 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:

Show 16 quoted lines

> Am 20.03.2011 05:32, schrieb Daniel:
>> 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?
>
> Not in the superproject, but you'll have your copy of the history
> of the submodule in its own .git directory on your harddrive.
>
>> 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).
>
> If the remote side vanishes you still have your local copy. And if
> you need to share that with others you can push the submodule
> somewhere else and adjust the .gitmodules entry accordingly.
>

Because I'm using it to version control my own home directory, and not all files are checked in to to git, this would post a problem for backup. I only back up the .git folder itself since it's all I need (running git checkout . to restore all the files) and individually selecting each file to restore is a lot of work.

Perhaps I just have an odd use-case.