Re: Breaking change with "git log -n" since 2.43

["Kristoffer Haugsbakk" <code@khaugsbakk.name>]

On Wed, Feb 21, 2024, at 15:21, Maarten Ackermans wrote:
> Whether or not that is Git's definition of a breaking change, the
> message of the commit in question acknowledges that the commands in
> the "log" family are the oldest in the system:

I was assuming Semantic Versioning (SV). Not because that’s the policy
in Git (?) but because this problem happened in a JS app./library. And
SV as far as I understand it define _breaking changes_ relative to the
“public API”. And for git-log(1) the public API is the documentation,
right?

(But maybe I’ve just never managed to understand SV.)

I also see now that this is some SV app./library.

-- 
Kristoffer Haugsbakk