From: Junio C Hamano <gitster@pobox.com>
To: Kato Kazuyoshi <kato.kazuyoshi@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] gitweb: add the ability to show side-by-side diff on commitdiff.
Date: Sun, 16 Oct 2011 18:51:07 -0700 [thread overview]
Message-ID: <7vbotgper8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAFo4x0+_Uy=yjbO61qj8krS0-iovzC5WnBE8-1n5OzxgGeg6JA@mail.gmail.com> (Kato Kazuyoshi's message of "Mon, 17 Oct 2011 10:15:07 +0900")
Kato Kazuyoshi <kato.kazuyoshi@gmail.com> writes:
> Probably like:
>
> - format_diff_line returns a class with an line.
> - remove trailing space from the class.
> - add side-by-side feature and CSS.
> - add form.
>
> Thank you for your correction!
My wording came out a bit too strong; I didn't mean to "correct" anything.
I think a better organization would be
[1/2] change code so that $diff_class does not have leading SP
optionally catch a case where $diff_class stays empty as an error?
[2/2] add side-by-side feature, which would involve:
- making format_diff_line() to return $diff_class separately;
- necessary addition of CSS;
- addition of form to trigger the feature.
I do not think splitting the second patch into pieces smaller than that
makes sense.
Thanks.
next prev parent reply other threads:[~2011-10-17 1:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 23:57 [PATCH/RFC] gitweb: add the ability to show side-by-side diff on commitdiff Kato Kazuyoshi
2011-10-17 0:20 ` Junio C Hamano
2011-10-17 1:15 ` Kato Kazuyoshi
2011-10-17 1:51 ` Junio C Hamano [this message]
2011-10-17 2:33 ` Kato Kazuyoshi
2011-10-17 3:57 ` 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=7vbotgper8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kato.kazuyoshi@gmail.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).