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

Re: [Issue 2458] New - check in after a force move doesnt work

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2005-12-05 13:12:45 CET

On 5 Dec 2005 11:08:35 -0000, madanus@tigris.org <madanus@tigris.org> wrote:
> http://subversion.tigris.org/issues/show_bug.cgi?id=2458
> Issue #|2458
> Summary|check in after a force move doesnt work
> Component|subversion
> Version|trunk
> Platform|All
> URL|
> OS/Version|All
> Status|NEW
> Status whiteboard|
> Keywords|
> Resolution|
> Issue type|DEFECT
> Priority|P3
> Subcomponent|src
> Assigned to|issues@subversion
> Reported by|madanus
>
>
>
>
>
>
> ------- Additional comments from madanus@tigris.org Mon Dec 5 03:08:29 -0800 2005 -------
> Hi,
> Checkin seems to lose the modified contents of a force moved file. The steps
> are as below
>
> - modify contents of file
> - do a svn move --force file newfilename
> - commit
> - checkout the repository in a different location
> - the modified contents are NOT available in the newly checkedout working copy
>
> But wait, what baffles me is...
> - modify contents of file
> - do a svn move --force file newfilename
> - modify contents of newfilename again
> - commit
> - checkout the repository in a different location
> - the modified contents are available in the newly checkedout working copy
>
> Am logging this issue without a discussion as its a very obviously wrong
> behavior. Pl. feel free to shread this into tatters if you think otherwise.
>
> Regards,
> Madan.

Madan,

Didn't Alexander and Karl find this bug and fix it on trunk, umm,
well, maybe a week or two ago?

bye,

Erik.
Received on Mon Dec 5 13:13:53 2005

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