Re: git-log --format missing trailing newline character

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Dec 23, 2024, 20:36 UTC
Message-ID: <d813a3dd-68c2-4cbe-92a0-cfd1ece77e9b@app.fastmail.com>
In-Reply-To: <cw7vyas4yw2q4lqiskbvil7mpkx5l5qilj25vnqzkrp5nuezrx@d6tsavm3ajzw>

On Mon, Dec 23, 2024, at 21:28, Alejandro Colomar wrote:

Show 17 quoted lines

> Hi!
>
> I'm having trouble scripting around git-log(1), due to a missing newline
> character at the end of the file.
>
> 	$ git -v
> 	git version 2.45.2
> 	$ git log --format=format:'%H' HEAD^^^..HEAD | wc -l
> 	2
> 	$ git log --format=format:'%H' HEAD^^^..HEAD
> 	2ff431ab1b46a25088fe40baf1faf35ea9fac722
> 	e75e6c4504022ae52d877926e63c908d9572088a
> 	178442837d39560a789a8044a8eb90fde3ad7cd7
>
> Would you mind fixing this bug?  POSIX requires that text files end in a
> newline character, precisely for being able to use UNIX tools to process
> output from arbitrary commands.

Is the format here simplified relative to your use case? Or do you just want to process commits as one-hash-per-line? I would use git-rev-list(1) instead in that case.

-- 
Kristoffer Haugsbakk