From: Thomas Rast <trast@inf.ethz.ch>
To: <git@vger.kernel.org>
Subject: [PATCH 0/2] log -L overlapping ranges
Date: Fri, 5 Apr 2013 16:34:46 +0200 [thread overview]
Message-ID: <cover.1365172322.git.trast@inf.ethz.ch> (raw)
I noticed that it doesn't like getting multiple overlapping ranges
from the user. This fixes it.
Thomas Rast (2):
log -L: check range set invariants when we look it up
log -L: fix overlapping input ranges
line-log.c | 43 +++++++--
t/t4211-line-log.sh | 6 ++
t/t4211/expect.multiple | 104 ++++++++++++++++++++
t/t4211/expect.multiple-overlapping | 187 ++++++++++++++++++++++++++++++++++++
t/t4211/expect.multiple-superset | 59 ++++++++++++
5 files changed, 392 insertions(+), 7 deletions(-)
create mode 100644 t/t4211/expect.multiple
create mode 100644 t/t4211/expect.multiple-overlapping
create mode 100644 t/t4211/expect.multiple-superset
--
1.8.2.662.g6b31d33
next reply other threads:[~2013-04-06 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 14:34 Thomas Rast [this message]
2013-04-05 14:34 ` [PATCH 1/2] log -L: check range set invariants when we look it up Thomas Rast
2013-04-05 14:34 ` [PATCH 2/2] log -L: fix overlapping input ranges Thomas Rast
2013-04-05 17:39 ` [PATCH 0/2] log -L overlapping ranges 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=cover.1365172322.git.trast@inf.ethz.ch \
--to=trast@inf.ethz.ch \
--cc=git@vger.kernel.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).