On Wed, Aug 10, 2016 at 03:56:02PM -0500, John Morris wrote:
> Thanks, Jeff. In the future, what would you guys prefer I do? Perhaps,
> when I want an automated build, push directly to glo; and when I want to
> propose a change set for merge, submit a Github PR?
If you have push access on glo
On 08/10/2016 03:48 PM, Jeff Epler wrote:
> On Wed, Aug 10, 2016 at 12:47:25PM -0500, John Morris wrote:
>> I just noticed that the issue tracker has moved to Github, and
>> linuxcnc.org/community now says PRs should be sent there. I love a lot
>> of things about Github, so that's great!
>>
>> I d
On Wed, Aug 10, 2016 at 12:47:25PM -0500, John Morris wrote:
> I just noticed that the issue tracker has moved to Github, and
> linuxcnc.org/community now says PRs should be sent there. I love a lot
> of things about Github, so that's great!
>
> I don't see that the LinuxCNC Github repo is inte
I just noticed that the issue tracker has moved to Github, and
linuxcnc.org/community now says PRs should be sent there. I love a lot
of things about Github, so that's great!
I don't see that the LinuxCNC Github repo is integrated with the
Buildbot, is that true? My PR#135 isn't being built,
