From: Junio C Hamano <gitster@pobox.com>
To: Mike Hommey <mh@glandium.org>
Cc: Duy Nguyen <pclouds@gmail.com>,
Thorsten von Eicken <tve@rightscale.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git status doesn't ignore GIT_DIR directory?
Date: Sat, 23 May 2015 10:00:23 -0700 [thread overview]
Message-ID: <xmqqwpzzcjq0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq1ti7dyky.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Sat, 23 May 2015 09:54:05 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I think both of you are wrong ;-)
>
> The thing is, what you are seeing does not have much to do with
> GIT_DIR. It is "what Git does when it finds a directory inside the
> working tree of a project". And ".git" is the only special thing in
> that context.
In short, I think Duy's "how about this" means well, but adds
documentation at a wrong place.
Having said all that, the message I am responding to showed the
right way to look at, understand, and explain the current behaviour.
It is a separate issue if the current behaviour is optimal from the
usability point of view. It is not entirely implausible to extend
the special casing rules from "a directory named '.git' only" to "in
addition, the directory pointed at by GIT_DIR, if exists, is treated
the same way".
next prev parent reply other threads:[~2015-05-23 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 1:03 git status doesn't ignore GIT_DIR directory? Thorsten von Eicken
2015-05-23 2:03 ` Junio C Hamano
2015-05-23 2:22 ` Duy Nguyen
2015-05-23 4:41 ` Thorsten von Eicken
2015-05-23 11:53 ` Duy Nguyen
2015-05-23 5:39 ` Mike Hommey
2015-05-23 11:42 ` Duy Nguyen
2015-05-23 16:54 ` Junio C Hamano
2015-05-23 17:00 ` Junio C Hamano [this message]
2015-05-23 17:39 ` 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=xmqqwpzzcjq0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.org \
--cc=pclouds@gmail.com \
--cc=tve@rightscale.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).