git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to fix (and find) many git-* --check errors?

From
PLPeter Valdemar Mørch (Lists) <4ux6as402@sneakemail.com>
Date
Aug 8, 2008, 12:49 UTC
Message-ID
<489C40BC.8000008@sneakemail.com>

We have > 37000 white space "errors" in HEAD, mostly trailing whitespace, and I'm looking for a

$ git diff --check | git??? --whitespace=fix
command.
Is there such a beast?

I see that git-apply has a --whitespace=<action> option, but I don't seem to grock how to be able to use it for fixing my working directory.

Details follow:

I can create a perl script that does this for me (e.g. inspired by 1.5.6's hooks/pre-commit's perl version of git diff --check) and post it here if anybody would like it, but I'd rather use some well-tested method if one exists. And it seems git-apply has the functionality somehow.

Of course, I can also:

$ git diff --check > tmpcfile # (Or some other command to find all of them under ./) $ vim :cfile tmpcfile

Thank you for --check having a handy output format, BTW! But I prefer automation (and automated auditing of the results) for 37000 lines.

Also the way I found them is like this:
$ git diff --check $(git log --pretty=format:%H | tail -1)..HEAD .

(The diff between "the empty commit" and HEAD - well between the first commit and HEAD anyway. Is there a ref for "totally empty" or the revision before the first commit? Or a more elegant way to get this list?)

Peter
-- 
Peter Valdemar Mørch
http://www.morch.com
Next: Jeff King
Message 1 of 6 in “How to fix (and find) many git-* --check errors?”
  1. Peter Valdemar Mørch (Lists)Aug 8, 2008
  2. Jeff KingAug 8, 2008
  3. Björn SteinbrinkAug 8, 2008
  4. Peter Valdemar Mørch (Lists)Aug 8, 2008
  5. Junio C HamanoAug 8, 2008
  6. Peter Valdemar Mørch (Lists)Aug 9, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.