From: Phil Hord <hordp@cisco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Heiko Voigt <hvoigt@hvoigt.net>,
Fredrik Gustafsson <iveqy@iveqy.com>,
git@vger.kernel.org, jens.lehmann@web.de
Subject: Re: [GSoC 11 submodule] Status update
Date: Thu, 30 Jun 2011 13:54:19 -0400 [thread overview]
Message-ID: <4E0CB84B.3060600@cisco.com> (raw)
In-Reply-To: <7vpqlws3jb.fsf@alter.siamese.dyndns.org>
On 06/29/2011 05:58 PM, Junio C Hamano wrote:
> Phil Hord <hordp@cisco.com> writes:
>> It frightens me because it seems like a fundamental break from the
>> current submodule functionality. Today a submodule exists as a git
>> repository with no knowledge that it is a submodule or who its
>> super-repository is.
> The use of .git that is a text file that records where the real directory
> is not limited to submodules. Placing that "real directory" somewhere in
> the .git directory of the superproject is merely a convention.
>
> In other words, it does not change anything fundamental.
Thanks for pointing that out. I was unaware of that feature until I saw
it discussed in another thread this week. Even then, it was not clear
to me that this is the same feature being employed here.
> When switching to another branch, a directory that does not exist in the
> switched-to branch needs to be removed, but we would refrain from "rm -fr"
> that directory if it has any leftover cruft in it (untracked and unignored
> files). A submodule directory should behave in the same way.
Thanks. I am suitably enclued and no longer afraid.
Phil
prev parent reply other threads:[~2011-06-30 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 19:34 [GSoC 11 submodule] Status update Fredrik Gustafsson
2011-06-28 0:29 ` Phil Hord
2011-06-28 18:43 ` Heiko Voigt
2011-06-29 21:27 ` Phil Hord
2011-06-29 21:58 ` Junio C Hamano
2011-06-30 17:54 ` Phil Hord [this message]
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=4E0CB84B.3060600@cisco.com \
--to=hordp@cisco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=iveqy@iveqy.com \
--cc=jens.lehmann@web.de \
/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).