On May 5, 2016, at 4:12 PM, webster.br...@rogers.com wrote:
>
> From: Branko Čibej
>
>> Not 'status' -- 'svn status' should always show what 'svn commit' will
>> send to the server. But 'diff', I agree, could be smarter. For example,
>> right now, 'svn diff --summarize -x -w' will mention files
You should wrapper the diff command
svn diff --diff-cmd 'diff -x -w' Brent
From: Branko Čibej
To: users@subversion.apache.org
Sent: Wednesday, May 4, 2016 11:01 PM
Subject: Re: Blank lines
On 04.05.2016 22:58, Daniel Shahaf wrote:
> Eric Johnson wrote on Wed, Ma
On 04.05.2016 22:58, Daniel Shahaf wrote:
> Eric Johnson wrote on Wed, May 04, 2016 at 09:42:53 -0700:
>> On 5/4/16 4:43 AM, Dariusz Staniak wrote:
>>> How can I force
>>> svn status
>>> not to indicate files with added/removed blank lines as modified?
>> You can't. Subversion has to treat all chan
Eric Johnson wrote on Wed, May 04, 2016 at 09:42:53 -0700:
> On 5/4/16 4:43 AM, Dariusz Staniak wrote:
> >How can I force
> >svn status
> >not to indicate files with added/removed blank lines as modified?
> You can't. Subversion has to treat all changes to files as relevant.
> Consider something li
Hi Darek,
On 5/4/16 4:43 AM, Dariusz Staniak wrote:
How can I force
svn status
not to indicate files with added/removed blank lines as modified?
You can't. Subversion has to treat all changes to files as relevant.
Consider something like Markdown - an extra blank line means a paragraph
break.
Hi Darek,
How can I force
svn status
not to indicate files with added/removed blank lines as modified?
I'm fighting with this all day today and I cannot find any help.
I've already changed diff-cmd and diff3-cmd to ignore blank lines, but
I still see these files as modified which gives me a jung
