Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Britton Kerin" <bkerin@fastmail.fm>
Cc: git@vger.kernel.org
Subject: Re: confusing GIT_DIR behavior case
Date: Mon, 17 Mar 2008 16:00:54 -0700	[thread overview]
Message-ID: <7v8x0harbt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1205793829.5984.1242927563@webmail.messagingengine.com> (Britton Kerin's message of "Mon, 17 Mar 2008 14:43:49 -0800")

"Britton Kerin" <bkerin@fastmail.fm> writes:

>    1.  GIT_DIR (and --git-dir) should make git behave exactly as if git
>    was 
>        wired to look for $GIT_DIR rather than '.git'.  The occurence of
>        the
>        GIT_DIR description in the top-level man page (for 'man git')
>        seems to
>        suggest that this is how things work.

That's underdescribing things.  Presense of GIT_DIR means much more than
that (e.g. you are at the top-level of the repository unless you have
WORK_TREE).

>    4.  The noob docs should make some mention of this issue.

Which "noob docs" did you look at (and do you think other people would
most likely to look at)?  I think the most important description they need
is not to mess with these environment variables.  It might sometimes be
needed to move .git away from its default place (and I haven't been in
that situation yet, so you have to be more advanced than me ;-)), but if
you are doing such a non-default thing, you are certainly no longer
"noob".

      reply	other threads:[~2008-03-17 23:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 22:43 confusing GIT_DIR behavior case Britton Kerin
2008-03-17 23:00 ` Junio C Hamano [this message]

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=7v8x0harbt.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=bkerin@fastmail.fm \
    --cc=git@vger.kernel.org \
    /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