git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nikolai Weibull" <now@bitwi.se>
To: "Pavel Roskin" <proski@gnu.org>
Cc: "Petr Baudis" <pasky@suse.cz>,
	"Timo Hirvonen" <tihirvon@gmail.com>,
	"Anand Kumria" <wildfire@progsoc.uts.edu.au>,
	git@vger.kernel.org
Subject: Re: ~/.git/config ?
Date: Sat, 27 May 2006 10:50:13 +0200	[thread overview]
Message-ID: <dbfc82860605270150s5c43e32fja2e7ef934bc1ef0@mail.gmail.com> (raw)
In-Reply-To: <1148697382.5599.1.camel@dv>

On 5/27/06, Pavel Roskin <proski@gnu.org> wrote:
> On Fri, 2006-05-26 at 18:38 +0200, Petr Baudis wrote:
> > Dear diary, on Fri, May 26, 2006 at 06:33:25PM CEST, I got a letter
> > where Timo Hirvonen <tihirvon@gmail.com> said that...
> > > I backup my $HOME using git, so there's a .git directory in ~.
> >
> > Then it should be called ~/.gitconfig. :-)
>
> No, make it .gitrc for compatibility with .cvsrc, .lynxrc and others.
>
> I know, it's becoming a bikeshed issue :-)

I want to paint part of it as well!

Wouldn't we be futureproofing ourselves by stuffing it in a
subdirectory instead?  What if we want to add more files later?

Also, can we please make sure to make the location of the file (or
directory) configurable through an environment variable, e.g.,
GIT_CONFIG, GIT_USER_CONFIG, GIT_HOME, or GIT_USER_HOME?

Peace.

  nikolai

  parent reply	other threads:[~2006-05-27  8:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26 15:28 ~/.git/config ? Anand Kumria
2006-05-26 16:33 ` Timo Hirvonen
2006-05-26 16:37   ` Jakub Narebski
2006-05-26 16:38   ` Petr Baudis
2006-05-26 17:05     ` Timo Hirvonen
2006-05-26 17:11       ` Petr Baudis
2006-05-27  2:36     ` Pavel Roskin
2006-05-27  2:57       ` Petr Baudis
2006-05-27  3:20         ` Linus Torvalds
2006-05-27  3:36           ` Linus Torvalds
2006-05-27  4:43             ` Junio C Hamano
2006-05-27  3:40           ` Jakub Narebski
2006-05-27  9:11           ` Junio C Hamano
2006-05-27 12:52           ` Horst von Brand
2006-05-28 21:59             ` [PATCH] Support for configurable git command aliases Petr Baudis
2006-05-28 22:57               ` Jakub Narebski
2006-05-29  3:58                 ` Jeff King
2006-05-29  2:01               ` Junio C Hamano
2006-05-29  8:02                 ` Petr Baudis
2006-05-27  8:50       ` Nikolai Weibull [this message]
2006-05-27  9:09         ` ~/.git/config ? Timo Hirvonen
2006-05-26 17:38 ` Junio C Hamano
2006-05-28 22:26 ` [PATCH] Read configuration also from ~/.gitrc Petr Baudis
2006-05-29  7:20   ` Johannes Schindelin
2006-05-29 14:00     ` Jakub Narebski

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=dbfc82860605270150s5c43e32fja2e7ef934bc1ef0@mail.gmail.com \
    --to=now@bitwi.se \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=proski@gnu.org \
    --cc=tihirvon@gmail.com \
    --cc=wildfire@progsoc.uts.edu.au \
    /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 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 NNTP newsgroup(s).