From: Daniel <daniel@netwalk.org>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: dependable submodules
Date: Sun, 20 Mar 2011 09:06:44 -0700 [thread overview]
Message-ID: <AANLkTimA-MKXrYfwE+WDOaPd7H1P6vvtcHTC6ODO5kAd@mail.gmail.com> (raw)
In-Reply-To: <4D85F4E1.1020607@web.de>
On Sun, Mar 20, 2011 at 5:36 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> 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.
next prev parent reply other threads:[~2011-03-20 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 0:53 dependable submodules Daniel
2011-03-20 4:27 ` Junio C Hamano
2011-03-20 4:32 ` Daniel
2011-03-20 12:36 ` Jens Lehmann
2011-03-20 16:06 ` Daniel [this message]
2011-03-21 16:18 ` Robert Pollak
2011-03-22 3:56 ` Daniel
2011-03-22 5:13 ` Avery Pennarun
2011-03-22 14:28 ` in-gitvger
2011-03-22 14:55 ` Daniel
2011-03-22 18:56 ` Jens Lehmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimA-MKXrYfwE+WDOaPd7H1P6vvtcHTC6ODO5kAd@mail.gmail.com \
--to=daniel@netwalk.org \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).