git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthias Lederhofer <matled@gmx.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: [PATCH] user-manual: set user.name and user.email with repo-config
Date: Sun, 28 Jan 2007 01:22:46 +0100	[thread overview]
Message-ID: <20070128002246.GA10179@moooo.ath.cx> (raw)
In-Reply-To: <20070127062826.GE14205@fieldses.org>

---
There are some other places where direct editing of .git/config is
suggested.  I'd rather tell the user to use repo-config and add a note
that repo-config saves the configuration to .git/config (or
~/.gitconfig with --global) which can be edited by hand too.
cat .git/config to show the remote configuration can be replaced by
git-repo-config -l | grep '^remote\.'
---
 Documentation/user-manual.txt |    7 ++-----
 1 files changed, 2 insertions(+), 5 deletions(-)

diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 87c605f..7a286d4 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -153,11 +153,8 @@ Making changes
 Make sure git knows who to blame:
 
 ------------------------------------------------
-$ cat >~/.gitconfig <<\EOF
-[user]
-name = Your Name Comes Here
-email = you@yourdomain.example.com
-EOF
+$ git repo-config --global user.name "Your Name Comes Here"
+$ git repo-config --global user.email you@yourdomain.example.com
 ------------------------------------------------
 
 Select file contents to include in the next commit, then make the
-- 
1.5.0.rc2.g18af

  reply	other threads:[~2007-01-28  0:22 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 ` Matthias Lederhofer [this message]
2007-01-28  0:32   ` [PATCH] user-manual: set user.name and user.email with repo-config 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
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=20070128002246.GA10179@moooo.ath.cx \
    --to=matled@gmx.net \
    --cc=bfields@fieldses.org \
    --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.
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).