git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Joey Hess <id@joeyh.name>
Cc: git@vger.kernel.org
Subject: Re: GIT_INDEX_FILE relative path breaks in subdir
Date: Mon, 23 May 2016 12:44:48 -0700	[thread overview]
Message-ID: <xmqqtwho8spb.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160523185258.GA10389@kitenet.net> (Joey Hess's message of "Mon, 23 May 2016 14:52:58 -0400")

Joey Hess <id@joeyh.name> writes:

>> I am not sure if relative to PWD is useful.  If it were relative to
>> either the GIT_DIR or the GIT_WORK_TREE, i.e. a fixed point, then
>> you can set and export GIT_INDEX_FILE and chdir around without
>> having to adjust it.  If it were relative to PWD, you would need to
>> adjust it every time you chdir, no?
>
> Good point, I had not considered this use case. Although if I set a
> long-term environment variable and expect to chdir around, well, that's
> what absolute paths are for. All my uses of GIT_INDEX_FILE
> are in short-term contexts where the program does not chdir.

Same to you.  I didn't consider a single-shot

	$ GIT_INDEX_FILE=./a-temporary-file-here git do something

It would be natural if we have that temporary file here where we
are in that use case.

      reply	other threads:[~2016-05-23 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 17:18 GIT_INDEX_FILE relative path breaks in subdir Joey Hess
2016-05-17 17:34 ` Junio C Hamano
2016-05-17 18:26   ` Joey Hess
2016-05-22 19:04     ` Joey Hess
2016-05-23 16:44       ` Junio C Hamano
2016-05-23 17:29         ` Joey Hess
2016-05-23 18:30           ` Junio C Hamano
2016-05-23 18:52             ` Joey Hess
2016-05-23 19:44               ` 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

  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=xmqqtwho8spb.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=id@joeyh.name \
    /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).