Re: Reducing "out-of-date" errors

Daniel Rall <dlr <at> collab.net> writes:

> You underestimate how often this situation arises in simpler
> Subversion deployment scenarios.
>
> I'm not saying "do it", just pointing out that in my experience, this
> is not an uncommon situation or use case.

The thread started out talking about this issue in the context of IDE plugins
and similar cases where you'd expect the Subversion implementation to be a
drop-in substitute for a CVS (or whatever) version.

May I suggest that it might make sense to keep the implementation of the "svn"
client as it is now, but for the implementors of Subclipse and so on to
automatically check after committing if an "update" would change any files, and
if not, execute it? This seems like a nice high-level heuristic, not
necessarily a core feature. Folks who like this behavior at the command line
could perhaps use a wrapper there, even.

--dave

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 2 07:34:21 2006