git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] log -L overlapping ranges

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 5, 2013, 17:39 UTC
Message-ID
<7vzjxcc1we.fsf@alter.siamese.dyndns.org>
In-Reply-To
<cover.1365172322.git.trast@inf.ethz.ch>
Thomas Rast <trast@inf.ethz.ch> writes:
> I noticed that it doesn't like getting multiple overlapping ranges
> from the user.  This fixes it.
Both look sensible.  Will queue on top of tr/line-log.
Thanks.
Previous: Thomas Rast
Message 4 of 4 in “log -L overlapping ranges”
  1. 0/2 log -L overlapping rangesThomas Rast, Apr 5, 2013
  2. 1/2 log -L: check range set invariants when we look it upThomas Rast, Apr 5, 2013
  3. 2/2 log -L: fix overlapping input rangesThomas Rast, Apr 5, 2013
  4. Junio C HamanoApr 5, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.