RetroSearch Browse

Sat Feb 26 18:36:02 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-February/108365.html

Am 26.02.2011 17:44, schrieb Antoine Pitrou:
> Le samedi 26 février 2011 à 08:38 -0800, Daniel Stutzbach a écrit :
>> On Fri, Feb 25, 2011 at 6:32 PM, Nick Coghlan <ncoghlan at gmail.com>
>> wrote:
>>         Would it be possible to name "trunk" as "2.x" instead?
>>         Otherwise I
>>         could see people getting confused and asking why trunk was
>>         closed,
>>         and/or not the same as "default".
>>
>>
>> Can we just get rid of "trunk" altogether?  It's history is a strict
>> subset of the 2.7 branch's history, isn't it?
> 
> Named branches are exclusive, they can't be a subset of each other ;)
> (in other words: 2.7 starts where trunk stops; trunk changesets are
> strict ancestors of 2.7)

But is there a need to have any changesets in the "trunk" named branch?
Couldn't the historical changesets just be in an unnamed branch, being
ancestor of so many named branches?

I'd like to prevent people from mistakenly committing onto the trunk,
which would be easiest if trunk didn't exist at all.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/108365.html below:

[Python-Dev] Mercurial conversion repositories