Re: Odd "diff" behavior

On Mon, Mar 24, 2008 at 11:19:51AM +0100, Karl Heinz Marbaise wrote:
> Hi Stefan,
> > stsp_at_ted [wc] $ svn cp a b
> > A b
> > stsp_at_ted [wc] $ svn diff
> > stsp_at_ted [wc] $ svn st
> > A + b
> > stsp_at_ted [wc] $ echo c > c
> > stsp_at_ted [wc] $ svn add c
> > A c
>
> Have you ever tried this:
>
> find -type f | xargs ls -al
> than you see things like this:
> .... .svn/entries
> .svn/format
> .svn/text-base/a
> .svn/text-base/b
> ./a
> ./b
> ./c
>
> > Why isn't the diff for b shown?
> > Was this a deliberate design decision?
> >
> And this is reason why svn diff will only print information for "c",
> cause it's building the difference between the pristine copy (.svn) and
> your working area. You see the missing "c" under .svn/text-base ?

OK, thanks for pointing that out.

So that is the way it's currently being done.

Augie and I were wondering why we don't compare files marked as
added-with-history against an empty file instead of the copy source?
Cause in essence, this would more accurately reflect the changes
that are about to be committed.

Was there a conscious decision behind this or did it simply evolve
from the facts you stated?

-- 
Stefan Sperling <stsp_at_elego.de>                 Software Developer
elego Software Solutions GmbH                            HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12        Tel:  +49 30 23 45 86 96 
13355 Berlin                              Fax:  +49 30 23 45 86 95
http://www.elego.de                 Geschaeftsfuehrer: Olaf Wagner