From: Junio C Hamano <junkio@cox.net>
To: Tom Prince <tom.prince@ualberta.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user-manual: set user.name and user.email with repo-config
Date: Sun, 28 Jan 2007 14:18:04 -0800 [thread overview]
Message-ID: <7vlkjmdcdf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vk5z7h9y5.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sat, 27 Jan 2007 23:44:34 -0800")
Junio C Hamano <junkio@cox.net> writes:
> Please, do not break people's scripts that still use
> repo-config.
Sorry for being terse. What I would prefer is no change to C
files except what is minimally needed to adding 'git-config' as
an alias to 'git-repo-config', plus s/repo-config/config/g in
the Documentation.
For Porcelains and test scripts shipped with git, replace
'repo-config' to 'config' only for actual strings used as
command names to be invoked, to play it safe (renaming a
variable 'repo_config' to 'config' needs to be done and verified
carefully as there may already be an existing variable 'config',
for example).
next prev parent reply other threads:[~2007-01-28 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 6:28 git user's manual J. Bruce Fields
2007-01-28 0:22 ` [PATCH] user-manual: set user.name and user.email with repo-config Matthias Lederhofer
2007-01-28 0:32 ` Linus Torvalds
2007-01-28 1:34 ` Matthias Lederhofer
2007-01-28 1:47 ` Linus Torvalds
2007-01-28 2:04 ` Junio C Hamano
2007-01-28 8:52 ` Jakub Narebski
2007-01-28 2:40 ` Tom Prince
2007-01-28 7:44 ` Junio C Hamano
2007-01-28 22:18 ` Junio C Hamano [this message]
2007-01-28 2:55 ` Nicolas Pitre
2007-01-28 8:50 ` Jakub Narebski
2007-01-28 23:34 ` J. Bruce Fields
2007-01-28 23:49 ` Linus Torvalds
2007-01-29 0:52 ` Junio C Hamano
2007-01-29 15:48 ` [PATCH] Make fsck and fsck-objects be builtins Mark Wooding
2007-01-29 17:35 ` Junio C Hamano
2007-01-29 6:39 ` [PATCH] user-manual: set user.name and user.email with repo-config J. Bruce Fields
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vlkjmdcdf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tom.prince@ualberta.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).