[Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

[Georg Brandl]

Am 02.07.2010 01:05, schrieb Antoine Pitrou:
> On Thu, 1 Jul 2010 15:26:12 -0700
> Brett Cannon <brett at python.org> wrote:
>> 
>> As I said, quick-and-dirty. It will take discussion to decide what we
>> want to ask non-committers to do,
> 
> I don't think we have to ask them to do anything special, as long as
> they can submit their contributions under the form of a patch.
> Whether they use named branches, separate clones, mercurial queues, the
> pbranch extension, or even the basic hg-as-an-svn-synonym workflow you
> suggested should be none of our business, IMO.
> 
> A DVCS allows non-committers to manage (augment, fix, synchronize) their
> patches more easily until they get committed. I don't think it will
> change the committers' work a lot, though. I don't know how Mercurial
> could make the task of committing an outsider's patch significantly
> simpler.

I do: if the outsider creates a patch in a personal branch, he is more
likely to merge with the trunk every now and then as if he creates a
patch once and then puts it on the tracker.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.