From: Junio C Hamano <junkio@cox•net>
To: Jakub Narebski <jnareb@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [RFC] Syntax highlighting for combined diff
Date: Sat, 21 Oct 2006 03:40:43 -0700 [thread overview]
Message-ID: <7v4ptygdec.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200610211202.00314.jnareb@gmail.com> (Jakub Narebski's message of "Sat, 21 Oct 2006 12:02:00 +0200")
Jakub Narebski <jnareb@gmail•com> writes:
> Junio C Hamano wrote:
>> Jakub Narebski <jnareb@gmail•com> writes:
>>
>> > Do I understand code correctly, and the last '+' or '-'
>> > in the parents column means?
>> >
>> > for (i = 0; i < ecbdata->nparents && len; i++) {
>> > if (line[i] == '-')
>> > color = DIFF_FILE_OLD;
>> > else if (line[i] == '+')
>> > color = DIFF_FILE_NEW;
>> > }
>> >
>> > Anyone who wrote this code, could you answer me, please?
>>
>> The "up to ecbdata->nparents" is Johannes in cd112ce. But you
>> are looking at a wrong code, I am afraid, if your original
>> question was about the combined format (there is a comment about
>> the codepath dealing only with two-way diffs by Johannes, above
>> the part you quoted). The output for combined diff is coming
>> from combine-diff.c:dump_sline().
>
> I was asking both about combined diff format, and how it is colored
> by git-diff --color, to add colored combined diff output to gitweb.
I was answering about both. dump_sline() implements both format
and coloring.
> Any other ideas how combined commitdiff should look like in gitweb?
Combined or no combined, one thing that mildly irritates me
sometimes is that there does not seem to be an easy and obvious
way to do a rough equivalent of typing SPACE repeatedly while
viewing "git log -p".
In other words, I think it would be a nice addition to have "go
to commitdiff page of this parent" links near the top on the
commitdiff page.
prev parent reply other threads:[~2006-10-21 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 0:35 [RFC] Syntax highlighting for combined diff Jakub Narebski
2006-10-21 7:48 ` Junio C Hamano
2006-10-21 8:49 ` Jakub Narebski
2006-10-21 9:41 ` Junio C Hamano
2006-10-21 10:02 ` Jakub Narebski
2006-10-21 10:40 ` Junio C Hamano [this message]
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=7v4ptygdec.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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