From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Hannu Koivisto <azure@iki.fi>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] user-manual: Simplify the user configuration.
Date: Sun, 25 Jan 2009 23:12:57 +0200 [thread overview]
Message-ID: <94a0d4530901251312q4201d51btd806fe860a12afd6@mail.gmail.com> (raw)
In-Reply-To: <7vvds3dszy.fsf@gitster.siamese.dyndns.org>
On Sun, Jan 25, 2009 at 10:34 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> It's much easier for everyone to just use git config --global than
>> explain how create and edit the .gitconfig file. If this is explained
>> it shouldn't be in the "Telling git your name" section.
>
> I think it is Ok to have, and it probably is helpful to have, a document
> that accompanies the generic manual, "Platform supplement", to explain
> things like "On this platform, what is referred to as $HOME in the generic
> manual is implemented as %HOMEDRIVE%%HOMEPATH%", to cover peculiarities of
> each platform.
>
> But I think it is going backwards to butcher the description in the main
> manual in order to make the platform supplement shorter. Even Windows is
> not a good enough reason to break the logical ordering of how things
> should be best taught to the readers of the manual, which is not specific
> to a platform.
That's why I think there should be a whole section regarding git
configuration before "Telling git your name".
However, my last proposal was to have both the git config --global
*and* the $HOME/.gitconfig description. Is there any argument against
that?
--
Felipe Contreras
next prev parent reply other threads:[~2009-01-25 21:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:09 [PATCH 1/2] user-manual: Simplify the user configuration Felipe Contreras
2009-01-21 18:09 ` [PATCH 2/2] Fix typo Felipe Contreras
2009-01-21 18:55 ` [PATCH 1/2] user-manual: Simplify the user configuration Markus Heidelberg
2009-01-21 19:04 ` [PATCH] " Felipe Contreras
2009-01-21 19:18 ` Jeff King
2009-01-21 19:39 ` Felipe Contreras
2009-01-21 19:51 ` Jeff King
2009-01-21 20:54 ` [PATCH 1/2] " Junio C Hamano
2009-01-21 21:13 ` Wincent Colaiuta
2009-01-21 21:19 ` Felipe Contreras
2009-01-22 16:17 ` Hannu Koivisto
2009-01-22 16:57 ` Felipe Contreras
2009-01-22 17:14 ` Junio C Hamano
2009-01-22 17:28 ` Johannes Schindelin
2009-01-22 18:59 ` Hannu Koivisto
2009-01-24 8:21 ` Felipe Contreras
2009-01-24 13:42 ` Johannes Schindelin
2009-01-24 14:04 ` Felipe Contreras
2009-01-25 20:34 ` Junio C Hamano
2009-01-25 21:12 ` Felipe Contreras [this message]
2009-01-25 21:44 ` Jeff King
2009-01-25 22:55 ` Wincent Colaiuta
2009-01-25 23:20 ` Jeff King
2009-01-25 7:32 ` Kyle Moffett
2009-01-25 12:06 ` 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=94a0d4530901251312q4201d51btd806fe860a12afd6@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=azure@iki.fi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).