On 25 May 2018 at 04:09, Ned Deily wrote:
> On May 24, 2018, at 13:46, Larry Hastings wrote:
> > On 05/24/2018 10:08 AM, Ned Deily wrote:
> >> If you (or anyone else) feels strongly enough about it, you should
> re-open the issue now and make it as a "release blocker" and we should
> discuss the
On Fri, May 25, 2018, 07:53 Nick Coghlan, wrote:
> On 25 May 2018 at 04:09, Ned Deily wrote:
>
>> On May 24, 2018, at 13:46, Larry Hastings wrote:
>> > On 05/24/2018 10:08 AM, Ned Deily wrote:
>> >> If you (or anyone else) feels strongly enough about it, you should
>> re-open the issue now and
If you create a dev branch that is going to live for less than 24 hours
because you edited some typo in the docs or something through GitHub's UI,
then that's fine. But long-lived dev branches should be done in one's
personal fork. This is for two reasons: one is so that others don't
inadvertently
On 5/25/2018 1:43 PM, Brett Cannon wrote:
If you create a dev branch that is going to live for less than 24 hours
because you edited some typo in the docs or something through GitHub's
UI, then that's fine. But long-lived dev branches should be done in
one's personal fork. This is for two reaso
On 25May2018 1043, Brett Cannon wrote:
(and because people often forget to do `git pull --prune`), and two
because it eats up our CI (which is especially precious while we are
still on AppVeyor and the turn-around time there is so long).
Don't we have branch filters on CI? (I certainly put the
