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

Re: svn add read-only-dir fails unrevertably

From: John Williams <williams_at_tni.com>
Date: 2004-11-04 00:08:32 CET

On 3 Nov 2004 kfogel@collab.net wrote:

> John Williams <williams@tni.com> writes:
> > Should I submit a bug for this? Seems like it should detect the
> > failure to create bad/.svn and avoid leaving the directory in the '~'
> > state.
> >
> > Is there any way to clean this up, besides editting ./.svn/entries by hand?
> It appears that current head (r11743) of Subversion behaves a bit
> differently. The 'svn status' never shows ~, instead it just gives an
> error. But, 'svn revert' works!

So that should be in the 1.2 release then. Something to look forward to.

> I think it's still a minor bug that the parent's .svn/entries file is
> left with the entry for the new directory, but that bug is fairly
> minor, given that 'svn revert' works on the bad directory and
> correctly cleans up the parent's .svn/entries file.
> So I'd say, file an issue, mark it as a P4 defect, put "bite-sized" in
> the keywords field, and drop the issue in the 'unscheduled' milestone.

I've created issue 2113, but I don't have access to the keywords and
milestone fields when adding, and I cannot edit issues either.

~ John Williams

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 5 17:06:27 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.