Not ideal, is it? I think that some system needs to be implemented.
-----Message d'origine-----
De : C. Michael Pilato [mailto:cmpilato@collab.net]
Envoye : mercredi 12 novembre 2003 16:10
A : Tim Armes
Cc : 'users@subversion.tigris.org'
Objet : Re: Hook error messages
Tim Armes <tarmes@fr.imaje.com> writes:
> Hi,
>
> I've just started using a hook to ensure that the log messages aren't
empty.
> Unfortunately, when a user tries to commit using a blank error message,
they
> simply get told that the merge operation has failed. Is there a way to
> improve this, so that the user gets told why it failed (i.e. "You must
> supply an log message") ?
Ideally, we'd be snarfing up stderr and sending that back to the user
(though... that might be a *whole* lotta data, hm...). Not sure what
to suggest here. Hey, worst-case, you could email the user. :-)
Dear <username>,
Recently you attempted a commit to the repository located at
http://my.server.com/repos/svn, but you failed to supply a
non-empty log message. You shall cease and desist from similar
errors of omission in the future -- or I'll be forced to dispatch
my team of expert thugs.
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 12 16:14:30 2003