Git development
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH 0/2] Introduce ~/.gitconfig
Date: Thu, 08 Jun 2006 09:02:29 -0500	[thread overview]
Message-ID: <1149775348.23938.236.camel@cashmere.sps.mot.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0606081329200.11910@wbgn013.biozentrum.uni-wuerzburg.de>

On Thu, 2006-06-08 at 06:30, Johannes Schindelin wrote:

> 
> - The name. I personally prefer .gitconfig, since we talk about the repo
>   config all the time. But I have no strong feelings there.

I like .gitconfig over .gitrc.

> - The --no-local flag could be implemented more cleanly, but also less

Could we have multiple levels, and have names that call out
where it applies?  Perhaps something like:

--repo   into $GIT_DIR/.gitconfig  <- current default, right?
--home   into ~/.gitconfig
--site   into /etc/gitconfig
--share  into /usr/share/git/config

My issue is that --no-local is vague and doesn't call out
where it actually does go.  There could be more than one
different non-local place.


> - With this, repo-config does no longer merit its name. What do people think
>   about making it a builtin named "git config"? (Of course, nothing hinders
>   us to keep the synonymous "repo-config" indefinitely...)

I have often forgotten the "repo-" part, and go looking
for the "git config ..." man page and command.  I think
it should be "git config".

Perhaps, "git repo-config"  would be "git config --repo ...."
And "git config ..." would need an explict --home, --repo,
--site type location flag from above?


But, hey, that's all pre-coffee.

jdl

  parent reply	other threads:[~2006-06-08 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 11:30 [PATCH 0/2] Introduce ~/.gitconfig Johannes Schindelin
2006-06-08 12:02 ` SV: " Sven Ekman
2006-06-08 12:06   ` Nikolai Weibull
2006-06-08 12:21     ` Johannes Schindelin
2006-06-08 13:13       ` Nikolai Weibull
2006-06-08 13:35         ` Johannes Schindelin
2006-06-08 14:02 ` Jon Loeliger [this message]
2006-06-08 14:49   ` Alex Riesen
2006-06-08 15:19   ` Johannes Schindelin
2006-06-08 18:32   ` Jakub Narebski
2006-06-08 20:15     ` Johannes Schindelin

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=1149775348.23938.236.camel@cashmere.sps.mot.com \
    --to=jdl@freescale.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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