Did you try the svn help command:
svn help diff
MB
--
You design it, I'll build it
e-mail: michael.l.br...@philips.com
desk: 608-288-6969
cell: 608-206-6843
> -Original Message-
> From: Andreas Tepe [mailto:andreas.t...@physics.gatech.edu]
> Sent: Monday, June 21, 2010 1:49 PM
> To: u
> -Original Message-
> From: Eiren Smith [mailto:eir...@gmail.com]
> Actually, for what it's worth in the current context, SVN has
> supported local log cacheing for a while. I don't recall which version
> introduced this feature, maybe 1.5 or 1.6.
>
> /eiren
We are currently at a version t
> -Original Message-
> From: Ryan Schmidt [mailto:subversion-20...@ryandesign.com]
> Working copies do not contain logs; "svn log" always connects to the
> repository.
Oh crap. Here I am thinking all this time that the working copy catually had a
copy of the log to work from. Ya, I know
> Michael,
>
> Thanks for jumping in.
>
> > If someone does have the area in question checked out, you'd have a
> > copy of the log in which to use to repair the repository.
>
> The revisions are not recent. Would the log of someone's working copy
> include binary deltas needed to recreate the actu
I'm sorta jumping in the middle of this, but doesn't anyone have a working copy
of the repository checked out, especially the area in question? Obviously no
one should have the whole trunk checked out, as people work with pieces of a
repository, specifically a branch, for example (like we do).
Yep, we use them.
MB
--
You design it, I'll build it
e-mail: michael.l.br...@philips.com
desk: 608-288-6969
cell: 608-206-6843
> -Original Message-
> From: Peng Yu [mailto:pengyu...@gmail.com]
> Sent: Monday, May 24, 2010 2:25 PM
> To: users@subversion.apache.org
> Subject: svn support fo
