From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Introduce ~/.gitconfig
Date: Thu, 08 Jun 2006 20:32:03 +0200 [thread overview]
Message-ID: <e69qev$nnl$1@sea.gmane.org> (raw)
In-Reply-To: 1149775348.23938.236.camel@cashmere.sps.mot.com
Jon Loeliger wrote:
> On Thu, 2006-06-08 at 06:30, Johannes Schindelin wrote:
>> - The --no-local flag [...]
>
> 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
I like that too, wlthough --home might be named --user, and --share be named
--predefined or --library.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-06-08 18:32 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
2006-06-08 14:49 ` Alex Riesen
2006-06-08 15:19 ` Johannes Schindelin
2006-06-08 18:32 ` Jakub Narebski [this message]
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='e69qev$nnl$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox