[Python-Dev] My patches
g.brandl at gmx.net
Thu Oct 30 23:26:11 CET 2008
Arfrever Frehtes Taifersar Arahesis schrieb:
> 2008-10-30 16:04 A.M. Kuchling <amk at amk.ca> napisał(a):
>> On Thu, Oct 30, 2008 at 11:04:42AM +0000, Barry Warsaw wrote:
>>> One of the reasons why I'm very keen on us moving to a distributed version
>>> control system is to help break the logjam on core developers. True, your
>>> code will still not be able to land in the "official" branch without core
>>> developer intervention, but you will be able to share your code, fixes,
>>> branches with everyone in a much more live way than patches in a tracker.
>> I don't see how a DVCS will fix anything. The bottleneck is in
>> assessing patches for inclusion in the master tree; not enough people
>> are doing that. We'd just end up with lots of proposed branches
>> waiting to be merged, instead of patches to be applied.
>> (What a DVCS might enable is making it easier to do larger
>> experiments, like the recent Vmgen work, and publish them in a form
>> that people can download. We could create SVN branches now, but that
>> means people would then have commit access to all of the Python
> SVN supports path-based authorization.
I don't see a problem with giving access to people wanting to work on
a branch, and telling them not to commit on the trunk.
We had and still have some such branches going on, e.g. for SoC students.
I also gave out access to several developers to work on the docs only,
or Sphinx which still is in Python's SVN repo.
After all, it's a VCS, and if someone plays against the rules, the commit is
reverted and the privs dropped in perhaps a minute.
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.
More information about the Python-Dev