git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jon Seymour" <jon.seymour@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: git rev-parse --git-dir does report yield relative path to git directory, per documentation
Date: Thu, 17 May 2012 13:23:04 -0500	[thread overview]
Message-ID: <20120517182304.GA14367@burratino> (raw)
In-Reply-To: <xmqqfwayrcen.fsf@junio.mtv.corp.google.com>

Hi,

Junio C Hamano wrote:
> Jon Seymour <jon.seymour@gmail.com> writes:

>> Per this advice in git-rev-parse(1):
>>
>>      Show $GIT_DIR if defined. Otherwise show the path to the .git
>> directory, relative to the current directory.
>> ...
[...]
> I am not sure what we were smoking.

Yeah, that text is pretty confusing.  Thanks for finding it.

The intent was:

	Show the path to the git repository database (usually $GIT_DIR or
	".git").  When relative, this path is relative to the current
	directory.

The point of that last part is that this is relative to the cwd when
rev-parse is called and not relative to the top level of the worktree.

  reply	other threads:[~2012-05-17 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  9:03 git rev-parse --git-dir does report yield relative path to git directory, per documentation Jon Seymour
2012-05-17 16:38 ` Junio C Hamano
2012-05-17 18:23   ` Jonathan Nieder [this message]
2012-05-18  9:23     ` [PATCH v1] Documentation: git-rev-parse: clarify that --git-dir does not necessarily show relative paths Jon Seymour
2012-05-18  9:31       ` Jonathan Nieder
2012-05-18 19:24         ` Junio C Hamano
2012-05-18 10:23       ` Nguyen Thai Ngoc Duy

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=20120517182304.GA14367@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jon.seymour@gmail.com \
    --cc=pclouds@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).