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

Re: [BUG] 'svn mv --force', 'svn ci' moves but doesn't commit local modifications

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2006-02-02 13:29:43 CET

On Tue, 31 Jan 2006, Philip Martin wrote:

> Daniel Rall <dlr@collab.net> writes:
>
> > cd /tmp/
> > rm -rf repos wc1 wc2
> > echo 'Setup a basic WC.'
> > svnadmin create repos
> > svn co file:///tmp/repos wc1
> > echo 'foo' > wc1/file.orig
> > svn add wc1/file.orig
> > svn ci -m 'Adding new file.' wc1/file.orig
> > echo
> >
> > echo 'Get a secondary WC'
> > svn co file:///tmp/repos wc2
> > # Now both WCs contain the file w/ same content.
> > echo
> >
> > echo 'Modify the contents of a file in the WC'
> > echo 'bar' >> wc1/file.orig
> > svn mv --force wc1/file.orig wc1/file.new
>
> It's a timestamp bug in mv/copy -- the text-time in the entries file
> erroneously matches the working file and so the local mod is not
> detected. If you manually "break" the timestamp
>
> touch wc1/file.new
>
> then the correct file contents get committed.
>
Seems like a regression of mine when I factored out
svn_wc_add_repos_file().

Will look at this ASAP.

Thanks,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 2 13:35:59 2006

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

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