All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@citi.umich.edu>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH 0/2] user-manual: reorganize the configuration steps
Date: Tue, 13 Oct 2009 22:49:40 -0400	[thread overview]
Message-ID: <20091014024940.GB9700@fieldses.org> (raw)
In-Reply-To: <1255293786-17293-1-git-send-email-felipe.contreras@gmail.com>

On Sun, Oct 11, 2009 at 11:43:04PM +0300, Felipe Contreras wrote:
> This basically introduces the "getting started" section so users get familiar
> with the configuration from the get-go, and also, most people prefer to teach
> 'git config --global' to setup the user name and email. Here are a few
> examples:

I'm not personally a big fan of starting out with a "how to use
git-config" section, because it's not that difficult or important:
questions we get on this list suggest confusion about a lot of things,
but git configuration is rarely one of them (that I've noticed).

I'd rather just point people to the git-config man page the first time
we mention any git configuration.  (And improve the man page if
necessary to ensure it's up to the job.)

If we have to do this, just keep it short....

--b.

> 
> git tutorial:
> http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
> 
> GNOME:
> http://live.gnome.org/Git/Developers
> 
> SourceForge:
> http://sourceforge.net/apps/trac/sourceforge/wiki/Git
> 
> github:
> http://help.github.com/git-email-settings/
> 
> Felipe Contreras (2):
>   user-manual: add global config section
>   user-manual: simplify the user configuration
> 
>  Documentation/user-manual.txt |   35 ++++++++++++++++++++++++++++++-----
>  1 files changed, 30 insertions(+), 5 deletions(-)
> 

  parent reply	other threads:[~2009-10-14  2:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11 20:43 [PATCH 0/2] user-manual: reorganize the configuration steps Felipe Contreras
2009-10-11 20:43 ` [PATCH 1/2] user-manual: add global config section Felipe Contreras
2009-10-11 20:43   ` [PATCH 2/2] user-manual: simplify the user configuration Felipe Contreras
2009-10-11 22:27   ` [PATCH 1/2] user-manual: add global config section Jonathan Nieder
2009-10-12 21:06     ` Junio C Hamano
2009-10-12 12:25   ` Michael J Gruber
2009-10-12 17:09     ` Felipe Contreras
2009-10-13  7:19       ` Michael J Gruber
2009-10-14 14:26         ` Felipe Contreras
2009-10-14 16:09           ` Michael J Gruber
2009-10-14 19:10             ` Junio C Hamano
2009-10-14  2:49 ` J. Bruce Fields [this message]
2009-10-14 14:14   ` [PATCH 0/2] user-manual: reorganize the configuration steps Felipe Contreras

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=20091014024940.GB9700@fieldses.org \
    --to=bfields@citi.umich.edu \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.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 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.