git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>, Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Sean <seanlkml@sympatico.ca>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [RFC] Renaming environment variables.
Date: Mon, 09 May 2005 19:16:03 -0700	[thread overview]
Message-ID: <7vy8anu8po.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0505091847050.30848-100000@iabervon.org> (Daniel Barkalow's message of "Mon, 9 May 2005 19:08:20 -0400 (EDT)")

>>>>> "DB" == Daniel Barkalow <barkalow@iabervon.org> writes:
>>>>> "PB" == Petr Baudis <pasky@ucw.cz> writes:

DB> While we're at it, it would be useful to have one for what is normally
DB> ".git", rather than just ".git/objects".

PB> I think it would be nice to have something like GIT_BASEDIR, which would
PB> default to .git, and the objects directory would then default to
PB> $GIT_BASEDIR/objects and the index file would default to
PB> $GIT_BASEDIR/index.

Although what I pushed out at git-jc repository does not have
this, it does not mean I forgot this issue you two have raised,
nor would want to veto it or anything like that.  Just that,
unlike the one that I already committed, the proposed change
would touch rather many lines and I have not managed to
determine the extent of the damage yet.

I am willing to make (or take) a separate patch to do this one,
since I agree with Petr's "currently we happen to have just two
but it would still be better to be able to set just one than
having to change both of them in sync." argument.

I am currently waiting for community consensus, including the
final name of the variable.  I think the current consensus is
that this is a good idea, the semantics for it is to name what
corresponds to the current "$(pwd)/.git" directory, use it to
build the default for GIT_INDEX_FILE and SHA1_FILE_DIRECTORY,
and this directory does _not_ have anything to do with my
previous "the directory that corresponds to the root of the tree
structure GIT_INDEX_FILE describes".  I agree to all of the
above.


  parent reply	other threads:[~2005-05-10  2:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 23:35 [PATCH] Introduce SHA1_FILE_DIRECTORIES Junio C Hamano
2005-05-07  0:20 ` Sean
2005-05-07  0:24   ` Junio C Hamano
2005-05-07  0:32     ` Sean
2005-05-07  6:31       ` Junio C Hamano
2005-05-07 19:51         ` Junio C Hamano
2005-05-09 13:33           ` H. Peter Anvin
2005-05-09 16:38             ` Junio C Hamano
2005-05-09 16:41               ` Sean
2005-05-09 18:03                 ` H. Peter Anvin
2005-05-09 18:50                   ` Junio C Hamano
2005-05-09 20:05                     ` [RFC] Renaming environment variables Junio C Hamano
2005-05-09 20:15                       ` Thomas Glanzmann
2005-05-10  0:32                         ` Petr Baudis
2005-05-09 21:04                       ` Sean
2005-05-09 23:08                       ` Daniel Barkalow
2005-05-10  0:09                         ` Junio C Hamano
2005-05-10  0:13                           ` Petr Baudis
2005-05-10  0:22                             ` Junio C Hamano
2005-05-10  0:27                               ` Petr Baudis
2005-05-10  0:38                           ` Daniel Barkalow
2005-05-10  0:44                             ` Petr Baudis
2005-05-10  0:53                               ` Daniel Barkalow
2005-05-10  5:45                             ` Junio C Hamano
2005-05-10  6:25                               ` Introducing GIT_DIR environment variable Junio C Hamano
2005-05-10 23:39                                 ` Alex Riesen
2005-05-10  2:16                         ` Junio C Hamano [this message]
2005-05-10  3:23                           ` [RFC] Renaming environment variables Daniel Barkalow
2005-05-10  0:25                       ` Petr Baudis
2005-05-10  1:02                         ` 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=7vy8anu8po.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=pasky@ucw.cz \
    --cc=seanlkml@sympatico.ca \
    --cc=torvalds@osdl.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.
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).