From: Junio C Hamano <gitster@pobox.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] init, clone: support --real-git-dir for .git file
Date: Fri, 04 Mar 2011 10:41:59 -0800 [thread overview]
Message-ID: <7vaaha7mo8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTiksQg1U=uAEVJG8fyjd7HpsTqgBOdyh6wrEMSED@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Fri\, 4 Mar 2011 19\:26\:16 +0700")
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> It's actually good that path is prefixed by gitdir. I imagine once
> superproject is supported, .git file in subprojects will have another
> line
>
> supergitdir: /path/to/superproject
No. On a platform with usable symbolic links, you should also be able to
solve "this version of the superproject has the submodule, but that
version does not, and we checkout the other version" with symlinking .git
without using a gitdir file at all, just like we can use .git/HEAD symlink
to denote the current branch.
Also, gitdir file is not for sole consumption of the submodule feature.
Keep separate things separate, and don't try to tie unrelated concepts
together.
next prev parent reply other threads:[~2011-03-04 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 12:43 [PATCH/RFC] init, clone: support --real-git-dir for .git file Nguyễn Thái Ngọc Duy
2011-03-03 21:13 ` Piotr Krukowiecki
2011-03-03 23:31 ` Junio C Hamano
2011-03-04 7:41 ` Piotr Krukowiecki
2011-03-04 12:26 ` Nguyen Thai Ngoc Duy
2011-03-04 18:09 ` Piotr Krukowiecki
2011-03-04 18:41 ` Junio C Hamano [this message]
2011-03-04 4:19 ` Nguyen Thai Ngoc Duy
2011-03-04 0:08 ` Junio C Hamano
2011-03-04 4:13 ` Miles Bader
2011-03-04 4:33 ` Nguyen Thai Ngoc Duy
2011-03-04 4:23 ` Nguyen Thai Ngoc Duy
2011-03-04 6:00 ` Junio C Hamano
2011-03-04 6:39 ` Nguyen Thai Ngoc Duy
2011-03-04 6:57 ` Miles Bader
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=7vaaha7mo8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=piotr.krukowiecki@gmail.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).