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

Re: [Subclipse-dev] Synchronization remaining problems

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-06-15 14:25:47 CEST

"Martin Letenay" <mle@whitestein.com> wrote on 06/15/2005 05:18:06 AM:

> I was thinking about the problem of incoming "just empty" directory,
resp. its
> cause (i.e. no kind information (file/dir) on added resources in "svn
status -u").
> I've implemented some workaround, but would like to ask you your
> We can reduce the number of "unknown" resources by properly sorting them
> deriving nodeKind information one some,
> but for the "leaves" of the repository tree, the information is just not

> available from svn update.
> However, if we sacrifice one or more server request round trips, we can
> the nodeKind information by subsequent calls to "svn list -r HEAD
> unkownResource(s)ParentDir".
> (Of course we can minimalize the number of the list request by propper
> grupping the unkown resources).
> It seems to work, but I'm not that expert on svn, so I'd like to ask you

> wheter you do not see some flaw there ...
> I believe we can trade off some speed for correctness in "synchronize
> repository" ...

I think it is worth trying. I would be willing to sacrifice some speed
for correctness.

I would have tried calling svn info for this. It seems like in the case
where there are not a lot of incoming changes it would be faster than
using svn ls. But it is just a guess.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Wed Jun 15 22:25:47 2005

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