On 26 Jun 2003, Ben Collins-Sussman wrote:
> Faheem Mitha <faheem@email.unc.edu> writes:
>
> > faheem ~/co/mg-ro>svn st
> > M mono
> > M mono/Makefile
> > A + mono/brent.cc
> > A + mono/brent.hh
> > M mono/debug.R
> > M mono/debug.cc
> > M mono/dist.cc
> > A + mono/getinv.c
> > D mono/int.cc
> > A + mono/inv.cc
> > M mono/mg.R
>
> You're aware of 'svn st -u', right? It will at least give you an
> overview of exactly how your working-copy is out-of-date, even though
> it won't show you the detailed diffs.
Yes. It doesn't make much difference for me, since I'm the only user here.
Usually I just use svn st to see which (if any) files I have modified.
> > faheem ~/co/mg-ro>svn diff --old file:///home/faheem/svn/brent --new
> > /home/faheem/co/mg-ro/mono
> >
> > but get
> >
> > svn: Working copy not locked
> > svn: directory not locked (/home/faheem/co/mg-ro/brent)
>
> Yes, I believe that after weeks of debate, Philip actually implemented
> this new 'svn diff' syntax. Unfortunately, there's no actual *code*
> in the back-end to support your use-case yet! See issue #1142.
Yes, I remember that long thread/discussion. For some reason I was left
with the impression that it had all been sorted out. I decided earlier
today to take a look at the open issues, and discovered 1142.
If you aren't going to be fixing this soon, perhaps consider replacing the
current error message with some "unimplemented functionality" type of
message.
Faheem.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 26 22:06:34 2003