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

Re: [PATCH] 'svn commit' of out-of-date items

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Mon, 28 Jan 2008 21:46:22 -0500

Stephen Butler <sbutler_at_elego.de> writes:
> A user has noticed that the handling of out-of-date conditions in
> 'svn commit' is inconsistent. For a single file, Subversion 1.4
> and 1.5 behave as follows.
> Case 1.
> Scheduled for deletion locally, modified in the repo.
> Error: File 'foo' is out of date
> Case 2.
> Modified locally, deleted in the repo.
> Error: File not found: transaction '2-3', path 'foo'
> Case 3.
> Scheduled for deletion locally, already deleted in the repo.
> No error, commit succeeds.
> The same applies to a directory with property modifications.
> Subversion issue #1017 led to a new commit test
> commit_out_of_date_deletions(), which covers case 1 above. The
> following diff ensures that the out-of-date error is raised for
> cases 2 and 3, and extends the test to cover those cases.

Stephen, I haven't had time to look at your patch closely, but I
wanted to make sure you were already aware of r27365 / issue #2740.
Your patch seems like it might be a continuation of that; if it's
applied, we should probably cross-reference the change with that other
revision and with the issue.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-29 03:46:46 CET

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