Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 6/2/2008 7:05 AM: > | > | I need a tool to automatically verify that ChangeLog > | and diffs are consistent. > > New enough git supports pre-commit hooks. I imagine we could probably > come up with a way to reject patches where the list of files touched > disagrees with the commit message, although I haven't attempted to do that > yet.
FYI, but for a compound error, I would have noticed this. I did run 'make distcheck' and even saw the usual traces of .lzma tarballs: =============================================================== coreutils-6.12.10-265c4-dirty archives ready for distribution: coreutils-6.12.10-265c4-dirty.tar.gz coreutils-6.12.10-265c4-dirty.tar.lzma =============================================================== however, my second error was in testing the wrong revision. Although I'd just fetched from a private repo to the current branch there (master), I'd neglected to sync the work area from the repository. The "-dirty" suffix should have tipped me off. _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
