On 10/24/2007 10:01 AM, Mark Phippard wrote:
> On 10/24/07, Jay Levitt <lists-subclipse@shopwatch.org> wrote:
>> At some
>> point, the WC became corrupted beyond cleanup's ability to fix things
>> (either Subclipse or command line); there were locked .svn/entries files
>> with a setguid bit set. I eventually had to manually copy all the
>> source files to a newly created directory, and sudo rm -rf the old stuff.
>
> Yes, that is the case. It is not because of the atomic moves though
> (that feature still has not been implemented). This bug was just an
> artificial limitation that Subversion carried around in its client
> API's. It did not allow something to be moved twice without a commit.
> This also manifests as not allowing a folder to be renamed, and then
> files in the folder also renamed. We try to work around the
> limitations in Subclipse but it is not hard to get to a point where it
> can't handle it anymore.
>
> 1.5 fixes all of this.
>
Oh, that's right - I think I remember a blog post (probably even yours)
talking about how that would be tough for Java refactoring, where
classes = filenames. Well, that sounds like as good an excuse to
upgrade as any, then. Plus I'll get to try your new merge client.
Jay
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Oct 24 16:24:49 2007