Subject: Re: [PATCH 0/2] line-log: small fixes

From: SZEDER Gábor <[email-masked]>
Date: Mon, 18 Aug 2025 13:25:47 +0200

On Mon, Aug 18, 2025 at 01:13:08PM +0200, SZEDER Gábor wrote:
> On Thu, May 02, 2024 at 09:29:04PM +0300, Evgeni Chasnovski wrote:
> > Calling `git log` with several `-L` flags can result in an error.
> > 
> > Steps to reproduce (on Linux):
> > - Set up repo with a history:
> >     - `mkdir log-line-assert`
> >     - `cd log-line-assert`
> >     - `git init`
> >     - `echo "Line 1\nLine 2" > file`
> >     - `git add .`
> >     - `git commit -m 'Commit 1'`
> >     - `echo "Line 3\nLine 4\nLine 5" >> file`
> >     - `git add .`
> >     - `git commit -m 'Commit 2'`
> > - Execute the following command: `git log -L2,2:file -L4,4:file`
> > 
> > # What did you expect to happen? (Expected behavior)
> > 
> > Show log with evolution of lines 2 and 4.
> > 
> > # What happened instead? (Actual behavior)
> > 
> > An error with the following text:
> > 
> > ```
> > git: line-log.c:73: range_set_append: Assertion `rs->nr == 0 ||
> > rs->ranges[rs->nr-1].end <= a' failed.
> > zsh: IOT instruction (core dumped)  git log -L2,2:file -L4,4:file
> > ```
> 
> Thanks for reporting this issue!

The original bug report is at:

  https://public-inbox.org/git/[email-masked]/

It's been quite a while since I last sent a patch to the list, and
apparently my send-email skills became somewhat rusty...