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

Re: Directory out-of-date (issue 987)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-11-14 17:24:47 CET

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> Philip Martin <philip@codematters.co.uk> writes:
> > Is it reasonable for 'svn commit' to fail with an out-of-date message
> > when 'svn status' doesn't show any out-of-date markers?
>
> I think it's merely expediency. If we could be more permissive (while
> still being correct, of course), that would be better.

Heh, even in the long run, I don't see how we could be more
permissive. This is exactly the same problem/reason we don't allow
propchanges on out-of-date directories. Adding/removing items to an
out-of-date directory is just as illegal.

This is the price we pay for allowing mixed-rev working copies.
Mixed-rev working copies are convenient, especially for files, but the
tradeoff is that sometimes you have to bring dirs up-to-date to do
versioning on them. Not a big deal. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 14 17:26:51 2002

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.