From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Phil Hord <phil.hord@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jens Lehmann <Jens.Lehmann@web.de>,
Antony Male <antony.male@gmail.com>,
git@vger.kernel.org, iveqy@iveqy.com
Subject: Re: [PATCH] Submodules always use a relative path to gitdir
Date: Fri, 6 Jan 2012 22:07:09 +0700 [thread overview]
Message-ID: <CACsJy8Agw6aTu=odeJXEbYuWQnE228w24_baP8u2eiX2-BEpeA@mail.gmail.com> (raw)
In-Reply-To: <CABURp0rFOFfX7eu-v6ZK07iTfXwhOne60d70GkCdOvx0k8BZkQ@mail.gmail.com>
On Fri, Jan 6, 2012 at 9:26 PM, Phil Hord <phil.hord@gmail.com> wrote:
> Do you see any _problem_ with making core.worktree a relative
> directory in the specific case of git submodules?
Not a problem per se, but you should look at the comment at the top of
t1510 to see where it is relative to. Two interesting rules:
2. .git file is relative to parent directory. .git file is basically
symlink in disguise. The directory where .git file points to will
become new git_dir.
3. core.worktree is relative to git_dir.
--
Duy
next prev parent reply other threads:[~2012-01-06 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 21:00 [PATCH] Submodules always use a relative path to gitdir Antony Male
2011-12-29 22:40 ` Junio C Hamano
2011-12-31 21:28 ` Phil Hord
2012-01-03 18:45 ` Junio C Hamano
2012-01-03 19:58 ` Junio C Hamano
2012-01-01 14:58 ` Jens Lehmann
2012-01-03 18:27 ` Junio C Hamano
2012-01-03 22:10 ` Jens Lehmann
2012-01-03 22:17 ` Junio C Hamano
2012-01-05 22:52 ` Jens Lehmann
2012-01-06 0:11 ` Junio C Hamano
2012-01-06 14:26 ` Phil Hord
2012-01-06 15:07 ` Nguyen Thai Ngoc Duy [this message]
2012-01-06 18:53 ` Junio C Hamano
2011-12-29 22:48 ` Fredrik Gustafsson
2011-12-31 20:31 ` Phil Hord
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='CACsJy8Agw6aTu=odeJXEbYuWQnE228w24_baP8u2eiX2-BEpeA@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=antony.male@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=iveqy@iveqy.com \
--cc=phil.hord@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).