Comments on: Git on Windows: “You have some suspicious patch lines”

By: jake rikimaru

jake rikimaru — Fri, 18 Dec 2009 16:25:33 +0000

Thx, saved me loads of frastration

By: Martin Carpella

Martin Carpella — Tue, 01 Dec 2009 17:29:15 +0000

@Blake I don't think it is crucial, but the core.autocrlf and core.safecrlf always works and I see no reason not to use it.

By: Blake

Blake — Tue, 01 Dec 2009 16:32:36 +0000

Thank you!
The initial solution really works, but as I’m not a big specialist in web-development, let me ask a question: developing with Ruby on Rails – do I need to care about trailing whitespaces?

By: Abhi

Abhi — Tue, 20 Oct 2009 16:30:38 +0000

Thanks a lot. This was very useful.

By: Git for Subversion Users | Wisdom and Wonder

Git for Subversion Users | Wisdom and Wonder — Sun, 05 Apr 2009 22:26:28 +0000

[...] Here is both an explanation of and a work-around for the error. To solve the problem, you need to edit .git/hooks/pre-commit and comment out the following lines: [...]

By: yaakuro

yaakuro — Fri, 27 Mar 2009 19:39:51 +0000

thx, saved my day too .

By: Rainer Blome

Rainer Blome — Mon, 15 Sep 2008 10:26:16 +0000

Sorry, that should have been
if (/[ \t]\r?\n?$/) {
bad_line(”trailing whitespace”, $_);
}

I don’t want to reject trailing whitespace other than space and tab.

By: Rainer Blome

Rainer Blome — Mon, 15 Sep 2008 10:14:15 +0000

My requirements are:

o By default I want it to be possible and safe to have files
with arbitrary line ending conventions in the same repository.
In general, I want Git to not modify content (not change line endings).
Put another way, it should just do what I tell it to do
(that may not be what I meant, but that is another issue).

o In order to be able to commit, the pre-commit hook needs to allow
the allowed line-ending conventions. For me, this does it:
if (/\s\r?\n?/) {
bad_line(“trailing whitespace”, $_);
}

By: Antony Stubbs

Antony Stubbs — Wed, 30 Jul 2008 09:39:55 +0000

I had this problem as well when I first started using Git, but today I ran into something else.

By: ben

ben — Thu, 17 Jul 2008 21:48:29 +0000

thanks for your solution, I had this problem on mac os x leopard and oucommenting

if (/\s$/) {
bad_line(“trailing whitespace”, $_);
}

in .git/hooks/pre-commit solved it