(Not sure if this was sent on the first attempt)
Also please have him subscribe to python-committers.
--
Eric.
Victor Stinner wrote:
Le vendredi 20 mai 2011 à 09:18 -0400, Jesse Noller a écrit : > Please make
sure he sends in a contributor agreement I am in contact with Charles-François.
I
On 4/9/2011 9:52 AM, Eric Smith wrote:
> On 04/09/2011 07:20 AM, Antoine Pitrou wrote:
>> Le jeudi 07 avril 2011 à 19:36 -0700, Brett Cannon a écrit :
>>>
>>> Hmmm so I assume Nadeem should send his SSH key to
>>> pydot...@python.org?
On 04/09/2011 07:20 AM, Antoine Pitrou wrote:
> Le jeudi 07 avril 2011 à 19:36 -0700, Brett Cannon a écrit :
>>
>> Hmmm so I assume Nadeem should send his SSH key to
>> pydot...@python.org?
>> Or?
>>
>> Nope, he can send them here to python-committers (you scared me
On 3/9/2011 7:53 AM, Antoine Pitrou wrote:
I completely agree with you - we have to make this process modern, and
simple. We just disagree on if it's necessary or not.
I hate arguments from authority, but here's the 2010 breakdown of
committers by changesets (thanks Mercurial :-)). Who do you
On 12/22/2010 8:46 AM, Georg Brandl wrote:
Am 22.12.2010 02:15, schrieb Nick Coghlan:
On Wed, Dec 22, 2010 at 6:18 AM, Georg Brandl wrote:
Since PEP 3003, the Moratorium on Language Changes, is in effect, there
are no changes in Python's syntax and built-in types in Python 3.2.
Minor nit - w
On 11/24/10 8:48 AM, Dirkjan Ochtman wrote:
All ssh repos can now be accessed by using ssh://h...@hg.python.org/repo
instead of ssh://h...@hg.python.org/repos/repo. While the old way should
continue to work, the new address should be considered preferable.
I'd suggest deleting the /repos/ URIs
Alexandre Vassalotti wrote:
On Tue, Mar 23, 2010 at 11:13 AM, Nick Coghlan wrote:
I'm not sure if there should be any change in the wording of the FAQ
entry for this - maybe expanding on the last sentence a bit?
Could we put a commit hook to prevent committing unintentional
"svnmerge.py init
Dirkjan Ochtman wrote:
On Wed, Mar 3, 2010 at 14:03, Eric Smith wrote:
Thanks, that's helpful.
But that's manually maintained, right? I was hoping to get something
generated from the svn configuration.
Unfortunately python-committers doesn't have real names for everyone, so
Jack Diederich wrote:
On Wed, Mar 3, 2010 at 7:47 AM, Eric Smith wrote:
We've been trying to ensure that everyone is on the [list]. To that end, is
there
somewhere I can regularly get an automated list of who has svn privileges?
http://www.python.org/dev/committers
Misc/developers.txt
> On Mar 03, 2010, at 07:30 AM, Jesse Noller wrote:
>
>>They're both on this list, right?
>
> I hope so! All committers are required to be.
Right, but sometimes they fall through the cracks. Subscribing to the list
should be in the "welcome packet" that new committers get, but it's a
somewhat man
>> The revisions in question are Victor's r78597 and Florent's r78621.
>> Since
>> these are not critical fixes, I am going to revert them.
>
> They're both on this list, right?
Yes, they are.
Eric.
___
python-committers mailing list
python-committers@p
Gregory P. Smith wrote:
On Mon, Mar 1, 2010 at 1:16 AM, Eric Smith wrote:
Steven Bethard wrote:
I'm preparing the argparse module for the 2.7 and 3.2 branches. Could
someone remind me again what the commit process is? Commit to 2.7 and
merge to 3.2? And do we merge with svnmerge.py o
Steven Bethard wrote:
I'm preparing the argparse module for the 2.7 and 3.2 branches. Could
someone remind me again what the commit process is? Commit to 2.7 and
merge to 3.2? And do we merge with svnmerge.py or svn merge? There's
probably a webpage explaining this somewhere, but my Google-fu is
Gregory P. Smith wrote:
What I've used when I'm merging a single revision is this:
I think the more pressing question that needs documenting is: "Given
that there are 4 active branches, in which order do I check things in
and merge them?"
Martin gave an answer to this on December 22, and
14 matches
Mail list logo
