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

[RFC] refer to post-patch lines in whitespace warnings

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jan 9, 2008, 15:57 UTC
Message-ID
<alpine.LNX.1.00.0801091046100.13593@iabervon.org>

When I rebase series with bad whitespace, I end up with unhelpful messages like:

.dotest/patch:412: trailing whitespace.
-- 
.dotest/patch:446: trailing whitespace.
-- 

These line numbers obviously refer to lines in a file that's been removed 
by the time I can do anything about it. It seems to me like the message 
would be more useful if, in the case where it leaves the working tree 
modified with the non-compliant whitespace, it gave this location rather 
than the patch's location (because, even if you have the patch still, 
you'd need to revert it first in order to be able to apply a fixed version 
anyway). Anybody see any problems with this theory?

	-Daniel
*This .sig left intentionally blank*
Next: Junio C Hamano
Message 1 of 4 in “[RFC] refer to post-patch lines in whitespace warnings”
  1. Daniel BarkalowJan 9, 2008
  2. Junio C HamanoJan 9, 2008
  3. Daniel BarkalowJan 9, 2008
  4. Junio C HamanoJan 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.