Flagging stable patches

Martin Geisler mg at lazybytes.net
Mon Jul 13 03:02:34 CDT 2009

Greg Ward <greg-hg at gerg.ca> writes:

> On Sun, Jul 12, 2009 at 8:07 PM, Matt Mackall<mpm at selenic.com> wrote:
>> Folks, please flag submitted patches that you think are suitable for
>> stable. Those will typically be fairly straightforward bug or doc fixes.
>> I'm going to try to do minor releases off -stable a bit more often this
>> time around. That damn lock.LockError bug got reported too many times.
> Great idea.  Even better would be if contributers used a common syntax
> for flagging stable patches.  May I humbly propose:
>   hg ci -m"(stable) foo: don't crash"
> resulting in
>   [PATCH] (stable) foo: don't crash
> The catch: it's up to whoever reviews/approves/commits/pushes to
> remove the "(stable) " prefix.

I'm very happy about my current pipe-mail-to-hg-import solution and
having to edit the patches would break that :-/ I could pipe through
sed, but I don't think one should automatically mangle patches.

On the other hand, I guess having "This is for stable." in the body is
not enough?

Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.

More information about the Mercurial-devel mailing list