From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Paul Mackerras <paulus@samba.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Better handling of local changes in 'gitk'?
Date: Thu, 12 Jul 2007 14:01:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707121356430.20061@woody.linux-foundation.org> (raw)
In-Reply-To: <7vejjdtkl0.fsf@assigned-by-dhcp.cox.net>
On Thu, 12 Jul 2007, Junio C Hamano wrote:
>
> I just meant that I agree with you that --cc between HEAD, index and the
> working tree is a wonderful way to view the current state.
Heh. I wasn't thinking of --cc, and if seen as a combination diff, I think
--combined would be better (we very much want to see *all* changes, not
just the conflicting ones, no?).
I was literally meaning two separate diffs, as two separate commits. But
yes, I do agree that it might be very interesting to make "git diff-index"
know about --combined/--cc in addition to --cached.
> It might make sense to teach "git diff" itself to show this
> 3-way diff with a new option ("git diff --h-i-w"). The
> necessary machinery is already there to handle "git diff maint
> master next pu" (four trees!), and "git diff maint:Makefile
> master:Makefile next:Makefile" (three blobs).
Actually, I think that if you teach "git diff-index" about --combined and
--cc, then you'll automatically get it when you just do "git diff HEAD".
No?
Linus
next prev parent reply other threads:[~2007-07-12 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 19:20 Better handling of local changes in 'gitk'? Linus Torvalds
2007-07-12 20:43 ` Junio C Hamano
2007-07-12 20:48 ` Junio C Hamano
2007-07-12 21:01 ` Linus Torvalds [this message]
2007-07-13 9:55 ` Paul Mackerras
2007-07-13 10:09 ` Paul Mackerras
2007-07-13 19:32 ` Linus Torvalds
2007-07-13 10:33 ` Johannes Sixt
2007-07-13 17:36 ` Linus Torvalds
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=alpine.LFD.0.999.0707121356430.20061@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.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).