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

Re: [PATCH] Issue #763

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-15 22:18:19 CEST

Scott Lamb <slamb@slamb.org> writes:
> And leaves the working copy as if the commit never happened. The patch
> leaves the working copy correct; it just doesn't warn that post-commit
> failed.


Frankly, I mildly prefer the current behavior, because:

   - Your working copy is not corrupt, it's just out-of-date; running
     "svn update" will Do The Right Thing and seamlessly merge the
     identical changes in. And if you blindly try to commit again,
     you'll get an out-of-date error, of course.

   - You find out that there's a problem with the post-commit hook.

The alternative is that your working copy looks committed, which is
nice, but you never learn that there's a problem with the post-commit
hook (or at least, you don't learn until someone thinks to ask where
the commit emails are, or whatever).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 15 22:29:58 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.