git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] gittutorial: Add global color.ui
Date: Mon, 13 Apr 2009 09:03:19 +0200	[thread overview]
Message-ID: <4d8e3fd30904130003m78dc7a81pf91ed6772b5c4f93@mail.gmail.com> (raw)
In-Reply-To: <20090410141622.10e40448@paolo-desktop>

Hello,
AFAIK the below path has not been commented or applied.

Should I just wait or does it means that is not considered usefull?

Regards,
        Paolo

On 4/10/09, Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
> I consider color.ui so important that I think it deserves to be mentioned in
> the gittutorial document.
> Patch is against pu.
>
> Signed-off-by: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
> ---
>  Documentation/gittutorial.txt |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt
> index c5d5596..6748fda 100644
> --- a/Documentation/gittutorial.txt
> +++ b/Documentation/gittutorial.txt
> @@ -44,6 +44,14 @@ $ git config --global user.name "Your Name Comes Here"
>  $ git config --global user.email you@yourdomain.example.com
>  ------------------------------------------------
>
> +This will make prettier the output of certain commands such as `git diff`
> +and `git branch`:
> +
> +------------------------------------------------
> +$ git config --global color.ui auto
> +------------------------------------------------
> +
> +
>
>  Importing a new project
>  -----------------------
> --
> 1.6.2.2.485.ge37347
>
>

  reply	other threads:[~2009-04-13  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 12:16 [PATCH] gittutorial: Add global color.ui Paolo Ciarrocchi
2009-04-13  7:03 ` Paolo Ciarrocchi [this message]
2009-04-13  7:29   ` 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=4d8e3fd30904130003m78dc7a81pf91ed6772b5c4f93@mail.gmail.com \
    --to=paolo.ciarrocchi@gmail.com \
    --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).