git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 7/7] user-manual: simplify the user configuration
Date: Sun, 5 Apr 2009 12:14:02 +0300	[thread overview]
Message-ID: <94a0d4530904050214y256cc0d3icc1843cfd148d69d@mail.gmail.com> (raw)
In-Reply-To: <76718490904042036q26bebc13p91c8cffaf432c02c@mail.gmail.com>

On Sun, Apr 5, 2009 at 6:36 AM, Jay Soffian <jaysoffian@gmail.com> wrote:
> On Sat, Apr 4, 2009 at 5:38 AM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> This is shorter, avoids the burder to think about the format of the
>> configuration file, and git config is already used in other places in
>> the manual.
>> [...]
>>  ------------------------------------------------
>> -[user]
>> -       name = Your Name Comes Here
>> -       email = you@yourdomain.example.com
>> +$ git config --global user.name "Your Name Comes Here"
>> +$ git config --global user.email you@yourdomain.example.com
>>  ------------------------------------------------
>
> This has come up before, and the idea was to hint to the reader that
> .gitconfig is something they can edit themselves.

Ok, I forgot to explain this again the commit message of this
particular patch, but it's described in the patch series description.

The previous patch adds a 'Getting Started' section that explains
exactly that; you can edit ~/.gitconfig.

So that concern is already addressed.

-- 
Felipe Contreras

  reply	other threads:[~2009-04-05  9:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04  9:38 [PATCH 0/7] user-manual: general improvements Felipe Contreras
2009-04-04  9:38 ` [PATCH 1/7] user-manual: remove some git-foo usage Felipe Contreras
2009-04-04  9:38   ` [PATCH 2/7] docbook: improve css style Felipe Contreras
     [not found]     ` <1238837909-3060-4-git-send-email-felipe.contreras@gmail.com>
2009-04-04  9:38       ` [PATCH 4/7] user-manual: use 'fast-forward' instead of 'fast forward' Felipe Contreras
2009-04-04  9:38         ` [PATCH 5/7] user-manual: use SHA-1 instead of SHA1 or sha1 Felipe Contreras
2009-04-04  9:38           ` [PATCH 6/7] user-manual: add global config section Felipe Contreras
2009-04-04  9:38             ` [PATCH 7/7] user-manual: simplify the user configuration Felipe Contreras
2009-04-05  3:36               ` Jay Soffian
2009-04-05  9:14                 ` Felipe Contreras [this message]
2009-04-05 15:11                   ` Jay Soffian
2009-04-05  9:47             ` [PATCH 6/7] user-manual: add global config section Junio C Hamano
2009-05-01  8:37               ` Felipe Contreras
2009-05-01 22:08                 ` Junio C Hamano
2009-05-01 22:51                   ` Felipe Contreras
2009-05-02  0:16                     ` Junio C Hamano
2009-04-06  8:14           ` [PATCH 5/7] user-manual: use SHA-1 instead of SHA1 or sha1 Junio C Hamano
2009-05-01  8:26             ` Felipe Contreras
2009-04-06  8:14         ` [PATCH 4/7] user-manual: use 'fast-forward' instead of 'fast forward' Junio C Hamano

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=94a0d4530904050214y256cc0d3icc1843cfd148d69d@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jaysoffian@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 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).