From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthias Lederhofer <matled@gmx.net>,
"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: Sat, 27 Jan 2007 18:04:35 -0800 [thread overview]
Message-ID: <7vodojhpos.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701271745000.25027@woody.linux-foundation.org> (Linus Torvalds's message of "Sat, 27 Jan 2007 17:47:49 -0800 (PST)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> What would also mean that we'd have the man-page with a simple
>
> man git-config
>
> which makes tons of sense if it documents both the config file *and* the
> "git config" program.
>
> Or is that too sneaky?
I like that.
If the solution can help us deprecate and eventually remove
git-var that would be ultra-nice.
next prev parent reply other threads:[~2007-01-28 2:04 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vodojhpos.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=matled@gmx.net \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.