From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config
Date: Mon, 28 Nov 2005 01:14:15 -0800 [thread overview]
Message-ID: <7vpsolxhg8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <438AC32E.5010100@op5.se> (Andreas Ericsson's message of "Mon, 28 Nov 2005 09:43:26 +0100")
Andreas Ericsson <ae@op5.se> writes:
> I'd still like to see git-repo-config and git-user-config. Otherwise
> we'll need to continue having user-based environment variables
> (GIT_COMMITTER_IDENT and friends).
Since .git/config is not shared across repositories even on
clone (and is deliberately so), "git-repo-config user.name" is
for you to set *your* name.
Having said that, GIT_COMMITTER_IDENT and friends are there to
stay, because that is how you override what you get from the
config file per commit, which is needed for people playing the
integrator role. When one is playing an individual developer
role, user.name or even not having any and relying on GECOS is
often good enough.
next prev parent reply other threads:[~2005-11-28 9:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 13:56 [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Johannes Schindelin
2005-11-21 15:44 ` Josef Weidendorfer
2005-11-21 15:57 ` Johannes Schindelin
2005-11-21 16:25 ` Josef Weidendorfer
2005-11-21 16:34 ` Andreas Ericsson
2005-11-21 22:26 ` Junio C Hamano
2005-11-27 12:59 ` Petr Baudis
2005-11-28 1:52 ` Johannes Schindelin
2005-11-28 6:22 ` Junio C Hamano
2005-11-28 8:43 ` Andreas Ericsson
2005-11-28 9:14 ` Junio C Hamano [this message]
2005-11-28 12:59 ` Josef Weidendorfer
2005-11-28 13:11 ` Andreas Ericsson
2005-11-28 14:32 ` Generic configuration plumbing (Was: Re: [RFC 2/2] Automatically transform...) Josef Weidendorfer
2005-11-28 15:26 ` Johannes Schindelin
2005-11-28 13:48 ` [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Petr Baudis
2005-11-28 15:03 ` Josef Weidendorfer
2005-11-29 6:04 ` Junio C Hamano
2005-11-28 16:29 ` Johannes Schindelin
2005-11-28 13:59 ` Petr Baudis
2005-11-28 16:33 ` 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=7vpsolxhg8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).