subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <webster.br...@rogers.com>
Subject Re: Blank lines
Date Thu, 05 May 2016 21:12:15 GMT
You should wrapper the diff command
svn diff --diff-cmd 'diff -x -w' ---- Brent

      From: Branko Čibej <brane@apache.org>
 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, 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 like Markdown - an extra blank line means a paragraph
>> break. In code, where inserting a blank line might help readability.
> Not quite.
>
> Internally, Subversion does have to use strict byte-for-byte comparisons
> (since committed files are preserved byte-for-byte in the repository).
>
> However, that has no bearing on the sense of comparison user-facing
> logic, such as 'diff' and 'status', should use: these could implement
> any sort of comparison deemed useful.  In particular, it might be useful
> for them to also be able to answer the question "What are all the files
> that have non-whitespace changes?".

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 that contain
only whitespace changes, even though 'svn diff -x -w' will show an empty
diff for those files.

-- Brane



  
Mime
View raw message