[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Reporter API cleanup for 1.0

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-12-29 06:55:34 CET

On Sun, 2003-12-28 at 16:44, Greg Hudson wrote:
> Actually, there's a much simpler answer: report paths should be
> anchor-relative. Since the anchor directory always exists and is never
> switched, the top level of the report would always legitimately *be* a
> set_path(), which would give the current reporter implementation a rev
> to hang a transaction off of.

That's not exactly true, I realized later; the anchor directory might be
locally added. (Why the client is interested in performing any server
operations other than "commit" on a locally added target, I'm not sure,
but you can run status and update and perhaps some other things. The
report presents them as belonging to revision 0. I'll document that
when I document the other practical peculiarities of reports.)

> Also, my new code could assume that edit
> paths and report paths are always the same.

I realized I can do this by normalizing the report paths to be
anchor-relative as I receive them.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 29 06:56:15 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.