From: Jonathan Nieder <jrnieder@gmail.com>
To: "Nathan W. Panike" <nathan.panike@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Document toplevel gitconfig file
Date: Sat, 27 Nov 2010 09:52:02 -0600 [thread overview]
Message-ID: <20101127155202.GA25598@burratino> (raw)
In-Reply-To: <f15d6598e5e90de3bcdb8caf706735ac4809ad36.1290870042.git.nathan.panike@gmail.com>
Nathan W. Panike wrote:
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -8,6 +8,17 @@ is used to store the configuration for that repository, and
> fallback values for the `.git/config` file. The file `/etc/gitconfig`
> can be used to store a system-wide default configuration.
>
> +One can also create a `.gitconfig` file in the toplevel of the
> +repository. This config file will then be propogated to collaborators
> +when they pull from your repository. Only `alias` config variables are
> +allowed to be set in this `.gitconfig` file. One can turn off the
> +shared `.gitconfig` by setting the environment variable
> +'GIT_CONFIG_NOSHARED' to 1; it will then be propogated but will not be
> +used for configuration settings.
Please no. Why not set up aliases in a setup-aliases.sh script and
mention it in your README?
If I clone a repository to investigate it and then a typo results in
$ git lgo
emptying my $HOME directory, I would not call that a feature.
next prev parent reply other threads:[~2010-11-27 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 15:00 [PATCH 0/2] Create a shared config file Nathan W. Panike
2010-11-25 17:21 ` [PATCH 1/2] Add support for " Nathan W. Panike
2010-11-27 16:29 ` Thiago Farina
2010-11-25 20:01 ` [PATCH 2/2] Document toplevel gitconfig file Nathan W. Panike
2010-11-27 15:52 ` Jonathan Nieder [this message]
2010-11-27 16:04 ` [PATCH 0/2] Create a shared config file Nguyen Thai Ngoc Duy
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=20101127155202.GA25598@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=nathan.panike@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.