On 7/14/06, Robert La Ferla <robertlaferla@comcast.net> wrote:
> I mistakenly posted this to the commit list instead of here:
>
> Subversion command-line client, version 1.3.2.
>
> After moving our SVN repository to another host (different machine
> with same host name), svn diff failed to work properly. I had a work
> area on the repository system and commited my changes locally. I
> then tried a "svn diff" from a remote client and it reported no
> changes! However, when I did a "svn update", it got all my changes.
>
> Seems to me (and I have not looked at the source) that the code that
> update uses to figure out what changed is different from the code
> that diff uses. This inconsistency is a bad thing.
> Also:
>
> On Jul 14, 2006, at 9:13 AM, Erik Huelsmann wrote:
>
> > Could you be a bit more specific? What commands did you use and what
> > output did they generate? What was the expected output and where are
> > the differences with what you actually got?
>
> svn diff
> svn update
>
> I expected "svn diff" to show the changes that I had commited to the
> repository. It didn't show anything at all.
'svn diff' reports changes in the working copy wrt the base version of
the working copy. Try 'svn diff -r HEAD' or, if you only want remote
changes 'svn diff -rBASE:HEAD'.
bye,
Erik.
PS: I suspected this would be the 'problem'. We call this 'user
error'. Could you post a bit more inquisitively instead of crying
loudly there are bugs in the software which are unacceptable? Lots of
people use these operations every day: this would have come out WAY
before you ever typed these commands.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 14 16:22:37 2006