On second glance it might involve having a file being committed that has CRLF endings in it. Committing files with LF only does not produce issue. I suspect git either needs to add support for a magic ignore line ending with a CRLF, or has to sanitize verbose output when that output has CRLF (less ideal) Bug originally seen as early as [2018](https://superuser.com/questions/1367811/sometimes-git-includes-the-diff-to-commit-message-when-using-verbose) On Tue, Oct 8, 2024 at 12:30 PM Spencer Fretwell <spencer.fretwell@xxxxxxxxx> wrote: > > gc -v produces CRLF file which does not ignore verbose description. > > OSX + git-annex (pre-commit hook disabled just in case) > using subl -w (sublime text 4) as editor, which indicated the change > in line endings > - committing as Unix fixes the issue (workaround, tedious) > - leaving as Windows is the issue > > see attached bugreport
