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

Re: Possible bug delete and revert

From: Peter McNab <mcnabp_at_optushome.com.au>
Date: 2006-12-19 12:02:56 CET

Žiga Osolin wrote:

> I deleted some files, then I placed new files (the same name upon
> them) and then I said revert, and SVN has overwritten the files. I
> think SVN should check if files exist before rewriting with the files
> last commited.
>
I'm not all that much in favor of this fundamental change in
Subversion's behavior.
Revert is revert is revert, or I feel should remain so.

The alternative scenario needs some though.

How would user's acceptance of the substitute file get committed?
1 or 2 commits.
1 Commit, meaning file content changed and hence history is maintained
even though the replacement file may be completely different in content.
2 Commits required, comprising the initial delete then add and commit so
new file' history starts now.
  What happens if the replacement file is in fact an uncommitted
Subversion "Renamed" file with previous history.

Peter (a non developer).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 19 13:43:24 2006

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