Documentation Bug 630652 created to install Guide update for Other Assets

Tom Bullock tbullock at
Mon Oct 4 08:09:30 EDT 2010

Sorry, forgot to reply all! Tom

-------- Original Message --------
Subject: 	Re: Documentation Bug 630652 created to install Guide update 
for Other Assets
Date: 	Mon, 4 Oct 2010 08:08:01 -0400
From: 	Tom Bullock <tbullock at>
Reply-To: 	Thomas Bullock <tbullock at>
To: 	Yawar Amin <yawar.amin at>


You said:

However, some diffing tools are very helpful in that they show you
end-of-sentence space characters with a colored background. The one I
use comes with Git (the version control software) and highlights extra
spaces in bright red, so they’re easy for me to find. Here’s a screen shot:
>  So in short–yes, I did go through your patch line by line to remove all the extra spaces, and committed the resulting patch into the repository. It was easy because of Git.
>  OK, you might think, why didn’t Trac show extra spaces in your patch [1]? Because Trac only show extra spaces as compared to what was there before, and since the chapter you wrote was completely new, Trac had nothing to compare it with and know that ‘Oh, these are extra spaces in here–I’ll highlight them in color’. I guess it’s a limitation. Some people might see it as a bug, others might say it’s not Trac’s job to show those spaces. The people who wrote Git decided that they wanted Git to be able to, and so it does.

   From prior discussions I agree that it is useful to remove "the
clutter" that extra spaces inject into the repository. I also have read
that, at least for now, there are some developers who continue to prefer
svn rather than switching to git.

What do you recommend how to quickly get familiar with git, at least
enough to be able to use its extra space disclosing feature? [Without
that, it seems to me it would be terribly laborious to find and remove
the extra white spaces.] Is there a good tutorial? What should I install
using Synaptic Package Manager? There are many modules that carry the
letters "git" in their names.



More information about the gnucash-devel mailing list