Saving info about each transaction (was Re: [PATCH 2 of 2] rollback: tell the user their previous commit message was saved)

Dirkjan Ochtman dirkjan at ochtman.nl
Sun Nov 22 14:55:16 CST 2009


On Sun, Nov 22, 2009 at 19:24, Greg Ward <greg-hg at gerg.ca> wrote:
> ...until you have a control-freak jerk (like me) enforcing policy in a
> pretxncommit hook.  Then you'll get a rollback every time your commit
> message references a bad bug ID, or you create a filename with spaces
> in it, or you commit source code with trailing whitespace, or a file
> with lines longer than 100 chars, ... whatever the local policy is
> that's enforced in a hook.
>
> IOW, workflows where there is more central control (like in a company,
> rather than an open-source project) might be more prone to fascist
> hooks and therefore more prone to rollback.

I should mention that the Python Mercurial server will also come with
a fair bunch of pretxncommit hooks (and I think Mozilla also has a
bunch of things there), so rejection in hooks seems like a valid use
case for rollback to me.

(I'm pretty interested in the things mentioned in this thread, it
seems to me some of the things this enables are long-standing feature
requests.)

Cheers,

Dirkjan


More information about the Mercurial-devel mailing list