From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: 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 09:22:56 +0700 [thread overview]
Message-ID: <20150523022256.GA17789@lanh> (raw)
In-Reply-To: <CAPc5daW2yTHHegPDrEWS5KiSYWZECV+AxMnewzz9ayASB1QNUw@mail.gmail.com>
On Fri, May 22, 2015 at 07:03:48PM -0700, Junio C Hamano wrote:
> As far as I know, GIT_DIR was prepared as a mechanism to point at
> another .git directory that does not live inside the working tree, not
> as a mechanism to rename it to arbitrary name. E.g.
>
> $ git init
> $ mv .git .svn
> $ GIT_DIR=$(pwd)/.svn ; export GIT_DIR
>
> is not expected to work.
This is not the first time we get this report. Perhaps we should
document it.
-- 8< --
Subject: git.txt: mention the special name ".git" in GIT_DIR
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 90c5f37..91d6dd2 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -691,6 +691,9 @@ Git so take care if using Cogito etc.
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.
++
+Note that if GIT_DIR is set explicitly to a directory inside working
+tree, the directory name must be ".git".
'GIT_WORK_TREE'::
Set the path to the root of the working tree.
-- 8< --
next prev parent reply other threads:[~2015-05-23 2:23 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150523022256.GA17789@lanh \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.