From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
git <git@vger.kernel.org>
Subject: Re: nd/setup
Date: Fri, 9 Apr 2010 08:56:46 +0200 [thread overview]
Message-ID: <l2ofcaeb9bf1004082356t2c304902l3f089b701299cec0@mail.gmail.com> (raw)
In-Reply-To: <20100409055701.GA9554@progeny.tock>
On Fri, Apr 9, 2010 at 7:57 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Nguyen Thai Ngoc Duy wrote:
>> 2010/4/8 Jonathan Nieder <jrnieder@gmail.com>:
>
>>> A few of the earlier patches seem iffy, though they all start with a
>>> correct idea. For example, one of them changes the semantics of
>>> rev-parse --show-prefix without documenting it. So I have been looking
>>
>> You meant "rev-parse --git-dir"?
>
> I meant --show-prefix. ad36c84 (worktree setup: calculate prefix even
> if no worktree is found, 2010-04-05) teaches rev-parse to produce a
> nonempty prefix even when there is no workdir but didn’t update the
> documentation:
>
> --show-prefix
> When the command is invoked from a subdirectory, show the
> path of the current directory relative to the top-level
> directory.
>
> I suspect it’s a good change. Git ought to correctly honor relative
> paths on the command line even when there is no work tree. But the
> semantics are not clear any more --- when there is no top-level
> directory, what is the prefix relative to?
>
> Probably my other words of warning were also too extreme. I have been
> using a copy of git with nd/setup included, and aside from the
> ls-remote problem I mentioned, I haven’t run into any trouble.
OK. I thought it was expectation and did not check documentation. The
assumption that $GIT_DIR stays at worktree's top directory is still
around.. I'll rethink about this.
--
Duy
next prev parent reply other threads:[~2010-04-09 6:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 0:48 What's cooking in git.git (Apr 2010, #03; Wed, 07) Junio C Hamano
2010-04-08 6:05 ` Johannes Sixt
2010-04-08 6:33 ` Junio C Hamano
2010-04-08 9:01 ` Fredrik Kuivinen
2010-04-08 9:14 ` ***SPAM*** " Tor Arntsen
2010-04-08 9:16 ` Tor Arntsen
2010-04-08 7:38 ` Jeff King
2010-04-08 21:42 ` nd/setup Jonathan Nieder
2010-04-09 0:13 ` nd/setup Jeff King
2010-04-11 11:01 ` [PATCH] Take it easy on unallowed access to non-existent repository Nguyễn Thái Ngọc Duy
2010-04-11 15:45 ` Sverre Rabbelier
2010-04-11 17:49 ` Nguyen Thai Ngoc Duy
2010-04-11 17:52 ` Sverre Rabbelier
2010-04-11 17:57 ` Nguyen Thai Ngoc Duy
2010-04-09 5:46 ` nd/setup Nguyen Thai Ngoc Duy
2010-04-09 5:57 ` nd/setup Jonathan Nieder
2010-04-09 6:56 ` Nguyen Thai Ngoc Duy [this message]
2010-04-11 17:57 ` nd/setup Nguyen Thai Ngoc Duy
-- strict thread matches above, loose matches on Subject: below --
2010-04-02 8:40 What's cooking in git.git (Apr 2010, #01; Fri, 02) Junio C Hamano
2010-04-02 11:23 ` Nguyen Thai Ngoc Duy
2010-04-03 5:00 ` nd/setup Jonathan Nieder
2010-04-03 14:39 ` nd/setup Nguyen Thai Ngoc Duy
2010-04-04 18:41 ` nd/setup Nguyen Thai Ngoc Duy
2010-04-04 21:42 ` nd/setup Junio C Hamano
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=l2ofcaeb9bf1004082356t2c304902l3f089b701299cec0@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).