From: plenz at cis.fu-berlin.de (Julius Plenz)
Subject: [PATCH 0/2] side-by-side-diff fixes
Date: Tue, 30 Oct 2012 13:56:00 +0100 [thread overview]
Message-ID: <1351601762-953642-1-git-send-email-plenz@cis.fu-berlin.de> (raw)
Two trivial fixes to the side-by-side-diff UI. It seems this UI is not
widely used, otherwise someone would have noticed...
Julius Plenz (2):
bugfix: in ssdiff, fix line number links
bugfix: make ss-diff correctly handle tab expansion
ui-ssdiff.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
1.7.12.3-zedat
next reply other threads:[~2012-10-30 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 12:56 plenz [this message]
2012-10-30 12:56 ` [PATCH 1/2] bugfix: in ssdiff, fix line number links plenz
2012-10-30 16:37 ` Jason
2012-10-30 12:56 ` [PATCH 2/2] bugfix: make ss-diff correctly handle tab expansion plenz
2012-10-30 14:56 ` plenz
2012-10-30 16:56 ` Jason
2012-10-30 17:12 ` plenz
2012-10-30 17:25 ` Jason
2012-10-30 17:52 ` plenz
2012-11-15 0:03 ` Jason
2012-11-15 16:35 ` [PATCH v2] " plenz
2013-02-01 12:51 ` Jason
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=1351601762-953642-1-git-send-email-plenz@cis.fu-berlin.de \
--to=cgit@lists.zx2c4.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).