Hi, Daniel,
> Von: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Okay, more seriously, here's a Vim script...
>
> The first two lines are the configuration, you shouldn't have to
change
> anything below them.
> [snap]
Thanks!
Best regards
Markus Schaber
___
We soft
Hi,
> Von: Stefan Sperling [mailto:s...@elego.de]
>
> On Tue, Jun 14, 2011 at 04:32:50PM +0200, Markus Schaber wrote:
> > Hi, Konstantin,
> > > A good policy is to educate the developers to commit
whitespace-only
> > > changes in a separate commit.
> >
> > I know that. And I'm searching for a too
Daniel Shahaf wrote on Wed, Jun 15, 2011 at 02:07:00 +0300:
> > Bonus points for a tool which keeps real indentation changes, and only
> > discards tab<->space conversions which do not change the indentation
> > level. :-)
>
> vim -c 'source /dev/mind-reader' -c 'wq'
>
> Not all OS's provide the
Markus Schaber wrote on Tue, Jun 14, 2011 at 11:47:48 +0200:
> Is there any tool which reverts all those whitespace-only changes,
> keeping only the "real" changes in the file?
>
svn diff foo > 1
svn revert foo
patch < ./1 || svn patch ./1
> Bonus points for a tool which keeps real indentation
On Tue, Jun 14, 2011 at 04:32:50PM +0200, Markus Schaber wrote:
> Hi, Konstantin,
> > A good policy is to educate the developers to commit whitespace-only
> > changes in a separate commit.
>
> I know that. And I'm searching for a tool allowing me to do just that.
>
> Especially when you make a se
Hi, Konstantin,
> Von: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
> > While Subversion and TortoiseSVN offer the possibility to ignore
those
> > white space changes when diffing the files, a commit still includes
> > those changes, and thus the diff in the SVN history is cluttered,
> > whi
2011/6/14 Markus Schaber :
>
> While Subversion and TortoiseSVN offer the possibility to ignore those
> white space changes when diffing the files, a commit still includes
> those changes, and thus the diff in the SVN history is cluttered, which
> causes problems for reviewers.
>
Maybe you can fin
Hi,
Occasionally, we have source files which contain - apart from the
changes made by the developer - a lot of whitespace changes introduced
by reformatting the code. (Mainly tabs<->spaces conversions and trailing
whitespace.)
While Subversion and TortoiseSVN offer the possibility to ignore those
