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

Re: white spaces in a patch

From
MRMark Ryden <markryde@gmail.com>
Date
Dec 17, 2008, 11:44 UTC
Message-ID
<dac45060812170344u368ffd7fx4e86253b4a13ffc7@mail.gmail.com>
In-Reply-To
<7vej07p84i.fsf@gitster.siamese.dyndns.org>
Hello,
I tried:
git apply patch1.txt
patch1.txt:34: trailing whitespace.
				
patch1.txt:53: trailing whitespace.

And "git diff" show differences but **does not** highlight anything. I tried in tchs and in Bash.

Any ideas ? does "git diff" does  highlight for anyone ?

Rgs, Mark

On Wed, Dec 17, 2008 at 9:34 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
> "Mark Ryden" <markryde@gmail.com> writes:
>
>> 1) Is there a way to check whether there are white spaces in this
>> file without running git-apply?
>
> "sed -n -e '/^+.*[      ]$/p' patch.txt" perhaps?
>
>> 2) Is there a way to get some messages about that there are white spaces
>> when creating a git patch?
>
> Doesn't "git diff" highlight whitespace errors?  That way, you can catch
> errors  before you make a commit that has them.
>
Previous: Junio C HamanoNext: Sverre Rabbelier
Message 3 of 12 in “white spaces in a patch”
  1. Mark RydenDec 17, 2008
  2. Junio C HamanoDec 17, 2008
  3. Mark RydenDec 17, 2008
  4. Sverre RabbelierDec 17, 2008
  5. Mark RydenDec 17, 2008
  6. Thomas JaroschDec 17, 2008
  7. Mark RydenDec 17, 2008
  8. Matthieu MoyDec 17, 2008
  9. Jeff KingDec 17, 2008
  10. Sverre RabbelierDec 17, 2008
  11. Johannes SchindelinDec 17, 2008
  12. Mark RydenDec 17, 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.