From: "Lars Hjemli" <hjemli@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: Intoducing the .git file (again)
Date: Sun, 17 Feb 2008 23:29:31 +0100 [thread overview]
Message-ID: <8c5c35580802171429m1091492dgd65e13c94de08bd4@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0802172219190.30505@racer.site>
On Feb 17, 2008 11:20 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Sun, 17 Feb 2008, Lars Hjemli wrote:
>
> > PPS: If included, the .git file should probably be used by git-submodule
> > to clone submodule repositories into something like
> > $GIT_DIR/submodules/<name>, as that would make local submodule changes
> > more resistant to dataloss due to checkout/reset in the containing
> > repository.
>
> I don't buy that argument. For the moment, the submodules are
> self-contained repositories. The superproject does not even have to have
> a single object contained in a submodule. I'd try to keep that
> separation.
They would still be separated and self-contained repositories, but
with my suggestion the submodule repository would be moved out of the
working tree of the containing repository. Which I believe is a good
thing, especially when you switch from one branch in the containing
repository which had the submodule in './foo' to another branch where
the submodule is located in './lib/foo'.
--
larsh
next prev parent reply other threads:[~2008-02-17 22:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 22:14 Intoducing the .git file (again) Lars Hjemli
2008-02-17 22:14 ` [PATCH 1/5] Add platform-independent .git "symlink" Lars Hjemli
2008-02-17 22:14 ` [PATCH 2/5] Fix setup of $GIT_DIR in git-sh-setup.sh Lars Hjemli
2008-02-17 22:14 ` [PATCH 3/5] Teach resolve_gitlink_ref() about the .git file Lars Hjemli
2008-02-17 22:14 ` [PATCH 4/5] git-submodule: prepare for the .git-file Lars Hjemli
2008-02-17 22:14 ` [PATCH 5/5] Teach GIT-VERSION-GEN about the .git file Lars Hjemli
2008-02-18 5:44 ` [PATCH 2/5] Fix setup of $GIT_DIR in git-sh-setup.sh Junio C Hamano
2008-02-18 8:41 ` Lars Hjemli
2008-02-17 22:25 ` [PATCH 1/5] Add platform-independent .git "symlink" Johannes Schindelin
2008-02-17 22:37 ` Lars Hjemli
2008-02-17 22:50 ` Lars Hjemli
2008-02-18 5:43 ` Junio C Hamano
2008-02-18 8:35 ` Lars Hjemli
2008-02-18 11:45 ` Johannes Schindelin
2008-02-17 22:20 ` Intoducing the .git file (again) Johannes Schindelin
2008-02-17 22:29 ` Lars Hjemli [this message]
2008-02-17 23:27 ` Johannes Schindelin
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=8c5c35580802171429m1091492dgd65e13c94de08bd4@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=Johannes.Schindelin@gmx.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).