Corrupted repository... help?

[Matt Mackall]

On Wed, Nov 21, 2007 at 09:25:03AM +0100, Martin Geisler wrote:
> Paul Sargent <psarge at gmail.com> writes:
> 
> > On 20 Nov 2007, at 19:07, Martin Geisler wrote:
> >
> >> I always hate it when I try to remove a SVN working copy and rm
> >> asks me
> >>
> >>  rm: remove write-protected regular file `working-copy/.svn/entries'?
> >>  rm: remove write-protected regular file `working-copy/.svn/format'?
> >>  ...
> >>
> >> and so on for quite a while.
> >
> > That's what '-f' is for; Surely.
> 
> Sure, I forgot to write that I use that flag in these case :-) But it
> still annoys me I have to force the deletion of those directories.
> 
> As long as I don't remove the write permission on my files I would
> expect to be able to delete a directory with 'rm -r' and then it is a
> (slight) surprice to have other programs remove the write permission.
> 
> I can see how having read-only files could be smart if we were sure
> that 'rm -r' would hit those files first. The user could then abort
> the deletion safely. But as far as I know there is no guarantee as to
> what order 'rm -r' uses, so when I get the warning it is of no use for
> for me.

Well we won't be doing that. Not only is it a nuisance in the way
described above (which often leads to even worse foot-shooting), but
it adds an extra two syscalls for each file!

-- 
Mathematics is the supreme nostalgia of our time.