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

Re: [BUG] Commit places working copy into bad state

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Wed, 14 May 2008 18:07:31 -0400

"Sebastian Celis" <svn-users_at_sebastiancelis.com> writes:
> On Wed, May 14, 2008 at 3:41 AM, Karl Fogel <kfogel_at_red-bean.com> wrote:
>> Yep, there's a bug here. Could you file an issue for it, so we don't
>> lose track, pointing back to your original mail?
> Thanks, Karl. I have filed an issue for the bug.
> http://subversion.tigris.org/issues/show_bug.cgi?id=3198
> I filed it as P1 because I could not determine a workaround in 1.5.0
> rc5. Plus, I can see the potential for data loss if there are other
> modified files in your working copy. The only way to retain those
> changes (including svn cp, svn mv, etc) is to perform a new checkout
> and then make every change again manually which could potentially be
> very hard to do if there are a lot of modified files. If you think it
> isn't that serious please let me know and I can drop it down to P3.
> Would you like me to also repost this to the dev mailing list? Or
> would you rather just leave it here and in the issue tracker?

Issue tracker is fine. Our Priority numbers are a vague guess at
(severity * likelihood), so I don't know what to say about P1 vs P3, but
in any case, I've started on a patch.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-15 00:07:54 CEST

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.