svn_client_log was where I had located the problem and tried to fix it and
got the core dump. I was trying to figure out how to debug the core dump
to figure out what was the cause but was running into trouble because of
the dynamically loaded modules...hmmmm, I *used* to be able to debug it,
why am I having problems now? Maybe I ought to try again, maybe I just
botched something. Maybe I shouldn't compile the debugging version with
dynamically loaded modules? That's the only difference I can think of...
I'll try again.
Thanks,
- David
On 7 Feb 2002, Ben Collins-Sussman wrote:
> David Summers <david@summersoft.fay.ar.us> writes:
>
> > I tried putting "svn log" in its place but "svn log" didn't know what to
> > do with the path to the repository. I'm actually looking at fixing that
> > bug but don't have any results yet, though I think I've found where to put
> > the fix, when I tried a fix the svn command bombed out and I haven't
> > figured out why yet.
> >
> > How about if the commit goes ahead with the understanding that it will be
> > switched to "svn log" as soon as that command is fixed?
> >
> > (Or maybe I'm missing something obvious)
> >
>
> No, you're right. 'svn log' currently requires a wc path. It
> currently converts an implicit '.' into a URL, then opens an RA
> session to that URL to fetch log messages. I bet in 10 minutes you
> could simply tweak svn_client_log() to be able to take a URL
> directly. I mean, it's already changing the wc-path into a URL
> anyway! Wanna give it a shot? :-)
>
>
--
David Wayne Summers "Linux: Because reboots are for upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:05 2006