[Python-Dev] Hg: inter-branch workflow

[Jesus Cea]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 17/03/11 14:45, R. David Murray wrote:
> Not if the cpython repo is in a fully merged stated.  And if it
> isn't, I will wait until it is.  (The update notifications on the
> IRC channel help with monitoring this.)

That is repository serialization. The point of HG is to avoid that :-).
Moreover, you are supposing that the original committer will merge "soon".

> If you leave an unmerged changeset in 3.2, I would consider that to be
> leaving the repo in a weird state.

I do agree. But there is nothing enforcing it (push hooks), except
social pressure.

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at 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 Mozilla - http://enigmail.mozdev.org/

iQCVAwUBTYJaTZlgi5GaxT1NAQJTmgP+IUCRioVAgSEjXtuufj3T6Vl1Q9XQCHej
4R+RTHeojTleWui3W013tS8cmQMa3Y8RSYh5G60kwhSZmdligRcDHWOzuTkemYol
QEv5DDx5dAK/n6XoRA4VWFkVWlw9ZQ8TiiQtvd8h5xiCSxFVTq9NB/LHCQTNzQrW
et/jGUvlkOI=
=oTMp
-----END PGP SIGNATURE-----