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

Re: Up-to-date-check on commit.

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-06-20 21:38:46 CEST

Peter Davis <peter@pdavis.cx> writes:
> Having to pass --force or any other option every time would be a terrible
> pain (I'm hardly ever at HEAD, especially when working on branches), but it
> would also be nice to have a little reminder that I am in fact not at HEAD.
>
> So I propose a compromise: check up-to-dateness for each commit, but make it
> only a WARNING condition if the check fails.

If we were going to do this, we should do it rather as a run-time
config option, you know, something like

   # Commits only allowed from completely up-to-date trees.
   strict_commits=yes

or whatever. (It's not a huge priority to do, IMHO, just that this
would be the way to go.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 20 21:46:19 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.