From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Syntax highlighting for combined diff
Date: Sat, 21 Oct 2006 12:02:00 +0200 [thread overview]
Message-ID: <200610211202.00314.jnareb@gmail.com> (raw)
In-Reply-To: <7vfydigg4w.fsf@assigned-by-dhcp.cox.net>
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.
> Combined diff output logic pretty much guarantees that you never
> will see plus and minus on the same line.
That's enough for me.
Any other ideas how combined commitdiff should look like in gitweb?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2006-10-21 10:02 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 [this message]
2006-10-21 10:40 ` 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=200610211202.00314.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.