![](https://secure.gravatar.com/avatar/66974ed16b5ad5293bac2d23005ff9a9.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 30/03/13 15:15, R. David Murray wrote:
This is the first time we've been in the situation of having a security-only branch in Mercurial (other than 2.7, which is its own head). So I don't believe we have articulated a procedure yet.
I am asking because the commit hook.
I expect patches will be few and far apart, so "somebody" could disable that hook just for committing those, when time comes. But I think would be interesting to actually think about it and document something now, even if we need to update it when we have real experience.
Something simple would be for the hook to refuse any commit in that branch UNLESS it is coming from the maintainer.
Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQCVAwUBUVcAa5lgi5GaxT1NAQKQ7gP/TZWs2pSqQs4K2Wc5jG6EZC52Ya7dGffT vhoWXhSBPCDuzzONh0BvPwVhMVGE6+IIBeUnxviCB/VnOfG7rNxcAb1GfwCWp0bY rtITu25Rgx3FemYyIROI1Bh0sdbWyEaEkgR6E+UEzO985fH7UJH24Ztc60ezyNgV Sn9KWXBdvOM= =ayOT -----END PGP SIGNATURE-----