From: Martin Nicolay <m.nicolay@osm-ag.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Martin Nicolay <m.nicolay@osm-ag.de>, git@vger.kernel.org
Subject: Re: bug: setting GIT_DIR to $(git rev-parse --git-dir) changes behavior
Date: Mon, 1 Mar 2021 09:08:31 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.20.2103010847410.20742@cpza.bfz-tzou.qr> (raw)
On Saturday 2021-02-27 22:06, Junio C Hamano wrote:
> Martin Nicolay <m.nicolay@osm-ag.de> writes:
>> *facepalm* The part about GIT_DIR setting the work-tree in addition to
>> the repository I hadn't read. How embarrasing.
>>
>> I apoligize for my bad reading skills and wasting you time.
>
> We would love to hear observations on which part of the
> documentation was misleading and suggestions on how to make it
> harder to misinterpret it.
There are multiple explanations regarding $DIR_DIR or --git-dir.
From git(1) two parts:
1)
--git-dir=<path>
Set the path to the repository (".git" directory). This can also be
controlled by setting the GIT_DIR environment variable. It can be
an absolute path or relative path to current working directory.
Specifying the location of the ".git" directory using this option
(or GIT_DIR environment variable) turns off the repository
discovery that tries to find a directory with ".git" subdirectory
(which is how the repository and the top-level of the working tree
are discovered), and tells Git that you are at the top level of the
working tree. If you are not at the top-level directory of the
working tree, you should tell Git where the top-level of the
working tree is, with the --work-tree=<path> option (or
GIT_WORK_TREE environment variable)
2)
GIT_DIR
If the GIT_DIR environment variable is set then it specifies a path
to use instead of the default .git for the base of the repository.
The --git-dir command-line option also sets this value.
The first part mentions the dual effect of setting git-dir, the second
not so.
As I had used GIT_DIR described in the second part, I feel vindicated ;-)
Hooray, instead of a software-bug I've found a documentation-bug.
My suggestion is to ammend the first sentence to something like "If the
GIT_DIR environment variable is set then it specifies a path to use
instead of the default .git for the base of the repository and also the
top-level directory of the working tree."
next reply other threads:[~2021-03-01 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:08 Martin Nicolay [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-26 7:54 bug: setting GIT_DIR to $(git rev-parse --git-dir) changes behavior Martin Nicolay
2021-02-27 21:06 ` Junio C Hamano
2021-02-25 14:54 Martin Nicolay
2021-02-25 18:29 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.20.2103010847410.20742@cpza.bfz-tzou.qr \
--to=m.nicolay@osm-ag.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).