From: Matthias Lederhofer <matled@gmx.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, git@vger.kernel.org
Subject: Re: [PATCH] user-manual: set user.name and user.email with repo-config
Date: Sun, 28 Jan 2007 02:34:52 +0100 [thread overview]
Message-ID: <20070128013452.GA11244@moooo.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.64.0701271625120.25027@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> I dunno. I really think that editing the config file is actually simpler.
>
> The "git repo-config" thing is really usefull from scripting, and for
> general automation, but maybe it's just me - I find human-readable ASCII
> files that you can put comments in etc just *nice*.
>
> I think the whole notion that you have to use a tool to edit
> configurations is asinine. It's good to have a tool for automation, but
> it's bad if that's the only way to interact with the system.
>
> The first time I had to use AIX, and realized that they do everything with
> some crazy system management tool, and that you can't do anything by
> editing files in /etc, I realized that IBM was totally incompetent when it
> came to UNIX.
>
> I mean, do people _really_ think that it's easier to do black magic
> scripts like
>
> git repo-config --global user.name "Your Name Comes Here"
>
> (which not only looks scary, but means that the user will never learn
> about the git config file at all), or just somebody saying:
>
> "Fill your .git/config file with
>
> [user]
> name = Your Name Here
> email = your@email.example
>
> and be happy"
>
> I'm just saying that the second example seems to not only be more
> human-friendly, it actually teaches people something that "git
> repo-config" never did.
>
> Maybe most users will just do what they are told without thinking about
> it, but then some users will look at that and say "Ahh, there's a
> .git/config file, I wonder what else I could do there.."
Good point, otoh the git-repo-config manual page is actually the one
documenting .git/config :). Therefore I think the manual should
mention git-repo-config(1) for information on .git/config with the
first use of the config file (actually the second because the first is
in part 1 which is only a list of commands).
Later in the manual git-repo-config is used to read (-l) and edit the
config file, perhaps there should be a short sentence that there is no
difference to editing .git/config directly.
---
user-manual: mention git-repo-config(1) with .git/config
---
Documentation/user-manual.txt | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 87c605f..509a867 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -603,7 +603,8 @@ $ cat .git/config
This is what causes git to track the remote's branches; you may
modify or delete these configuration options by editing .git/config
-with a text editor.
+with a text editor. See gitlink:git-repo-config[1] for more
+information on .git/config.
Exploring git history
=====================
--
1.5.0.rc2.g18af
next prev parent reply other threads:[~2007-01-28 1:35 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 [this message]
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=20070128013452.GA11244@moooo.ath.cx \
--to=matled@gmx.net \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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).