git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Color support for "git-add -i"
Date: Thu, 06 Dec 2007 12:18:47 -0800	[thread overview]
Message-ID: <7vejdzd1aw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <5055E3DF-E01D-41B5-9F59-DAD69885CAE8@wincent.com> (Wincent Colaiuta's message of "Thu, 6 Dec 2007 20:59:48 +0100")

Wincent Colaiuta <win@wincent.com> writes:

> What are the other options?
>
> - Make git-add--interactive part of builtin-add so as to be able to  
> use the core.whitespace code directly? (ideally yes and at some point  
> in the future it seems inevitable that this will happen, but it will  
> require a fair bit of work)
>
> - Fork a second "git diff-files" process to capture the colorized  
> version of the output? (may set off the "kludge" alarm)
>
> - Something else?

 - Realize that whitespace clean-up can be risky and change semantics
   depending on the material you are editing.  Do not do the clean-up
   during "add -i", but before.  IOW, add an alias that does an
   equivalent of:

	git diff HEAD >tmp
        git apply -R <tmp
        git apply --whitespace=fix <tmp

   then encourage users to clean-up their whitespace gotchas early (and
   test the result!), before even attempting to run "git add -i".

  reply	other threads:[~2007-12-06 20:19 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         ` [PATCH 0/3] Reroll colorized "git add -i" Junio C Hamano
2007-12-06  5:40         ` [PATCH 3/3] Color support for "git-add -i" Jeff King
2007-12-06 19:59         ` Wincent Colaiuta
2007-12-06 20:18           ` Junio C Hamano [this message]
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=7vejdzd1aw.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=win@wincent.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).