RE: libsvn_client checkout and multiple targets

From: Ben Collins-Sussman [mailto:sussman@collab.net]
> <peter.westlake@arm.com> writes:

> > Furthermore, with separate checkouts in a loop there is scope for
> > someone to check in a change in between. The projects won't have the

> > same revision number.

> Actually, it looks like that's exactly what Bill is trying to avoid in

> his patch. Instead of fetching the "latest" revision of each project
> in a loop, he converts apr_time_now() into a revision number, and then
> sticks to that particular tree throughout the loop.

Exactly. To tell you the truth, I don't have much prefence about how the

directory process works, I'd just like to put all of that mess into
libsvn_client
and let it do all of the fun work. I wass wondering if anybody objected
to the
approch I used in my patch in order to get the job done.

I'm guesing not, but lots of people got stuck on the user visible
behavior
vs. the actual patch.

I'll go ahead and try and implement the idea as Fitz's not mentioned to
be cvs like.
If people think we need to change it, so much the better.

Once I get this code straightened out I can actually finish up the goop
to get the SVN client COM object up and running on its separate thread.

Bill

---------------------------------------------------------------------
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:36:37 2006