From: Junio C Hamano <junkio@cox.net>
To: Mark Wooding <mdw@distorted.org.uk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] config: Rummage through ~/.gitrc as well as the repository's config.
Date: Fri, 03 Feb 2006 17:15:09 -0800 [thread overview]
Message-ID: <7vacd7c4bm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20060203203332.2718.13451.stgit@metalzone.distorted.org.uk
Mark Wooding <mdw@distorted.org.uk> writes:
> I'm fed up of setting user.email in every repository I own.
That is what --template-dir to init-db is for (it works in an
already initialized git repository, but it does not overwrite
files).
> I want to put this somewhere central, and I shouldn't have to
> log in again to make it take effect.
I do not understand about logging in again. If you are talking
about environment variables, ". ~/.env" would work nicely.
next prev parent reply other threads:[~2006-02-04 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 20:33 [PATCH] config: Rummage through ~/.gitrc as well as the repository's config Mark Wooding
2006-02-04 1:15 ` Junio C Hamano [this message]
2006-02-04 10:22 ` Mark Wooding
2006-02-04 12:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vacd7c4bm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mdw@distorted.org.uk \
/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).