git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Thorsten von Eicken <tve@rightscale.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git status doesn't ignore GIT_DIR directory?
Date: Sat, 23 May 2015 18:53:41 +0700	[thread overview]
Message-ID: <CACsJy8B7tUiRqw0ogLFaHfDo2RwVN8BP09uBQBGVOA9eHtWLvw@mail.gmail.com> (raw)
In-Reply-To: <556004DE.7080504@rightscale.com>

On Sat, May 23, 2015 at 11:41 AM, Thorsten von Eicken
<tve@rightscale.com> wrote:
> On 5/22/2015 7:22 PM, Duy Nguyen wrote:
>> 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.
>>
>> ++
>> +Note that if GIT_DIR is set explicitly to a directory inside working
>> +tree, the directory name must be ".git".
> This is not at all what I was hoping to hear, but thanks for the response.

To elaborate a bit more, I think ".git" was cooked in the code near
the beginning and for too long. By the time people wanted flexibility,
".git" string was already all over the place and changing it may
require some (and maybe big) code reorganization, and all that is for
a rare use case.. I think I saw at least two attempts to fix this but
they went nowhere. On the bright side, you can work around this easily
by adding ".svn" to your ignore list.
-- 
Duy

  reply	other threads:[~2015-05-23 11:54 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 [this message]
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

  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=CACsJy8B7tUiRqw0ogLFaHfDo2RwVN8BP09uBQBGVOA9eHtWLvw@mail.gmail.com \
    --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.
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).