git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] Reroll colorized "git add -i"
Date: Wed,  5 Dec 2007 18:05:06 -0800	[thread overview]
Message-ID: <1196906706-11170-4-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <1196906706-11170-3-git-send-email-gitster@pobox.com>

Another try of the colorized "git add -i" series.

[PATCH 1/3] Documentation: color.* = true means "auto"

This is a documentation fix that has already been applied to 'master'
(not pushed out yet as of this writing).

[PATCH 2/3] git config --get-colorbool

This allows scripts to figure out if they should use colors.

[PATCH 3/3] Color support for "git-add -i"

This is Dan's colorized git-add -i, but uses --get-color and
--get-colorbool options to git-config.

  reply	other threads:[~2007-12-06  2:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 10:59 [PATCH] Color support for "git-add -i" Junio C Hamano
2007-12-05 12:21 ` Johannes Sixt
2007-12-05 13:52   ` Wincent Colaiuta
2007-12-05 19:46   ` Junio C Hamano
2007-12-06  2:05   ` [PATCH 1/3] Documentation: color.* = true means "auto" Junio C Hamano
2007-12-06  2:05     ` [PATCH 2/3] git config --get-colorbool Junio C Hamano
2007-12-06  2:05       ` [PATCH 3/3] Color support for "git-add -i" Junio C Hamano
2007-12-06  2:05         ` Junio C Hamano [this message]
2007-12-06  5:40         ` Jeff King
2007-12-06 19:59         ` Wincent Colaiuta
2007-12-06 20:18           ` Junio C Hamano
2007-12-07 12:34             ` Wincent Colaiuta
2007-12-06  5:30       ` [PATCH 2/3] git config --get-colorbool Jeff King
2007-12-06  5:35         ` Jeff King
2007-12-06  6:12         ` Junio C Hamano
2007-12-06  6:17           ` Jeff King
2007-12-06  7:38         ` Eric Wong
2007-12-05 13:55 ` [PATCH] Color support for "git-add -i" Wincent Colaiuta

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=1196906706-11170-4-git-send-email-gitster@pobox.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.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 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).