On Fri, Mar 18, 2011 at 5:00 AM, Jesus Cea <j...@jcea.es> wrote: > -----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 :-).
The easier merging in Hg means that it *is* easy to work offline, or even against separate clones. Trying to keep a clean history in the main repository so committer responsibilities are tracked correctly is still a reasonable goal. > Moreover, you are supposing that the original committer will merge "soon". What may actually be better for buildbot experimentation purposes is to allow us to request running a build-and-test cycle from branches in *any* of the repositories hosted on hg.python.org, rather than having to push experimental changes to the main line of development. (i.e. start moving towards more of a style of development where code doesn't land in the main repository until it has been vetted by the buildbots *first*). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
