> I realize that is what it is doing, and I want to continue doing it. What
> I was acknowledging was that the high-level Subscriber implementations
> make it difficult to use svn status -u. I was merely speculating on ways
> we might be able to use the high-level API but still use svn status -u.
I can't really see how we can build the svn subscriber on top of a
high level api. You could give it a try thought, I am sure some good
ideas will come up.
> > If you look at the cvs code you will find that many CVS actions also
> > interfere with the Subscriber.
> Are you saying there are cases where the CVS Synch view exhibits some of
> the same problems that we have?
No but looking at the CVS code I saw some 'dirty' code that was
written in the Eclipse 3.0 rc cycles that was trying to solve some
issues that arized during the 3.0 stabilization phaze.
Maybe should document or even better try to create testcases for the
problems. If we do that we could try to see what is causing them and
try solve them one by one.
Received on Mon Jan 10 00:28:03 2005
This is an archived mail posted to the Subclipse Dev