On 08/02/17 17:06, Jesus Cea wrote:
> On 08/02/17 16:18, Jesus Cea wrote:
>> I am trying to convince him to launch buildbot process tree with an
>> "ulimit" to protect the machine. Lets see.
>>
>> Sorry. Thanks for your patience.
>
> I am launching now the buildbot with a limit of 1GB *PER PROCESS
On Wed, 8 Feb 2017 at 15:04 Victor Stinner wrote:
> 2017-02-08 23:42 GMT+01:00 Brett Cannon :
> > Don't forget we are doing squash merges,
>
> Ah, I didn't know. Why not using merges?
>
Because other core devs wanted a linear history. This preference was very
strong to the point people were will
On 09.02.2017 00:03, Victor Stinner wrote:
2017-02-08 23:42 GMT+01:00 Brett Cannon :
Don't forget we are doing squash merges,
Ah, I didn't know. Why not using merges?
Same question here. I see no benefit just overhead, mistakes and longer
processes.
Sven
_
2017-02-08 23:42 GMT+01:00 Brett Cannon :
> Don't forget we are doing squash merges,
Ah, I didn't know. Why not using merges?
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
On Wed, 8 Feb 2017 at 13:33 Victor Stinner wrote:
> 2017-02-08 21:32 GMT+01:00 Terry Reedy :
> > Many patches have multiple authors. Does the 'author' field allow that?
> > Often, the committer adds missing chunks or rewrites the work with
> various
> > degrees of editing. Sometimes a read a pat
2017-02-08 21:32 GMT+01:00 Terry Reedy :
> Many patches have multiple authors. Does the 'author' field allow that?
> Often, the committer adds missing chunks or rewrites the work with various
> degrees of editing. Sometimes a read a patch for the idea and then start
> fresh with the actual code.
On Wed, 8 Feb 2017 at 12:33 Terry Reedy wrote:
> On 2/8/2017 2:38 AM, Victor Stinner wrote:
>
> > I know that different people have different expectation on GitHub. I
> > would like to take the opportunity of migrating to Git to use the
> > "author" and "committer" fields. If the author is set to
On 2/8/2017 2:38 AM, Victor Stinner wrote:
I know that different people have different expectation on GitHub. I
would like to take the opportunity of migrating to Git to use the
"author" and "committer" fields. If the author is set to the real
author, the one who proposed the change on the bug t
On Tue, 7 Feb 2017 at 23:38 Victor Stinner wrote:
> 2017-02-08 8:35 GMT+01:00 Victor Stinner :
> > I'm sure the patch author would appreciate it, but I don't think we
> > need to require it as we have gone this long without it.
>
> I know that different people have different expectation on GitHub
On 08/02/17 16:18, Jesus Cea wrote:
> I am trying to convince him to launch buildbot process tree with an
> "ulimit" to protect the machine. Lets see.
>
> Sorry. Thanks for your patience.
I am launching now the buildbot with a limit of 1GB *PER PROCESS*. At
least, when the memory skyrockets it wi
On 08/02/17 11:24, Victor Stinner wrote:
> So I suggest to drop official Solaris support, but I don't propose to
> remove the C code specific to Solaris. In practice, I suggest to
> remove Solaris and OpenIndiana buildbots since they are broken for
> months and are more annoying than useful.
The m
On 08/02/17 11:24, Victor Stinner wrote:
> So I suggest to drop official Solaris support, but I don't propose to
> remove the C code specific to Solaris. In practice, I suggest to
> remove Solaris and OpenIndiana buildbots since they are broken for
> months and are more annoying than useful.
Give
On 02/07/2017 11:38 PM, Barry Warsaw wrote:
On Feb 07, 2017, at 02:15 PM, Mike Miller wrote:
Does anyone know why Python 3.6 is not the default Python 3 under the
upcoming Ubuntu Zesty, or what may be holding it back?
I guess that would be me. :)
Thank for the in-depth explanation!
The
Hi,
Is there anything new about Solaris or OpenIndiana since September?
Right now, it seems like the cea-indiana-x86 buildbot slave is offline
since longer than 54 days.
Oracle decided to stop Solaris 12 development:
https://arstechnica.com/information-technology/2017/01/oracle-sort-of-confirms-d
On 07/02/2017 22:38, Barry Warsaw wrote:
On Feb 07, 2017, at 02:15 PM, Mike Miller wrote:
Does anyone know why Python 3.6 is not the default Python 3 under the
upcoming Ubuntu Zesty, or what may be holding it back?
I guess that would be me. :)
Is there anyone that could give it a nudge? It
15 matches
Mail list logo