Re: [PATCH] * HACKING (Avoid trailing white space): Mention how git can help.

[Jim Meyering]

Ralf Wildenhues wrote:
> * Jim Meyering wrote on Mon, Mar 02, 2009 at 10:34:41PM CET:
>>
>> Good idea.  Thanks!
>> I'll push this tomorrow, unless you'd prefer something else.
>
> How about this instead?  I looked at git a bit more, and have
> little experience with git apply (not sure whether it's used
> all over the place or not), so let's make that less prominent.

Thanks Ralf.
Looks good, but I had to make an additional change,
since the procedure changed in git-1.5.6.1.

>From 937ade894d77d16f3ba39d2547b68d55e330d3ad Mon Sep 17 00:00:00 2001
From: Ralf Wildenhues <address@hidden>
Date: Mon, 2 Mar 2009 22:33:05 +0100
Subject: [PATCH] * HACKING (Avoid trailing white space): Mention how git can 
help.

---
 HACKING |   19 +++++++++++++++++++
 1 files changed, 19 insertions(+), 0 deletions(-)

diff --git a/HACKING b/HACKING
index 0675f9c..ad3e39f 100644
--- a/HACKING
+++ b/HACKING
@@ -380,6 +380,25 @@ If you use vim, add this to ~/.vimrc:
     match RedundantSpaces /\s\+$\| \+\ze\t/


+Git can help too, by stopping you from committing any change that would
+add trailing blanks.  The example pre-commit hook contains code to check
+for trailing whitespace and spaces before tabs; enable it by moving it
+to the right place and making sure it is executable:
+
+    mv .git/hooks/pre-commit.sample .git/hooks/pre-commit
+
+With a repository created by git-1.5.6 or older, use this command:
+
+    chmod +x .git/hooks/pre-commit
+
+To manually check for whitespace errors before committing, you can use
+
+    git diff --check
+
+Git also has some settings to enable suitable internal whitespace checks.
+See the manpage for git-apply for details.
+
+
 -------------------------------------------

 Miscellaneous useful git commands
--
1.6.2.rc1.285.gc5f54