> > Also, Mojca brought the question of the hundreds of open tickets with
> > port submissions a while back. It might be neat if we had some code
> > that caused a special Github account to generate a PR for a port
> > submission in trac. I wouldn't want this automatically invoked (at
> > least
(Not a member, speaking from a user point of view.)
On Apr 01 12:02:23, pe...@piermont.com wrote:
> As some of you have noticed, I've been trying to keep the PR queue
> relatively clear.
Thank you for that! It really is rewarding
to see the PRs being acted upon in a timely manner,
as opposed to
(I noticed that my previous email was flying to some strange address.
I'm sorry if this is the second post, I cannot see the other one in
mail archive, so I'm not sure if it went through.)
On 4 April 2018 at 16:28, Jonathan Stickel wrote:
>
> Some instructions about
> recommended procedures for
On Apr 4, 2018, at 07:18, Mojca Miklavec wrote:
>>> Also, Mojca brought the question of the hundreds of open tickets with
>>> port submissions a while back. It might be neat if we had some code
>>> that caused a special Github account to generate a PR for a port
>>> submission in trac. I
I like the idea of a trac to PR script or something to make things easier.
The github API is pretty easy to use, but I’m not a trac expert by any
means. That said, I’d be willing to help.
—Mark
On Wed, Apr 4, 2018 at 8:18 AM Mojca Miklavec wrote:
> On 4 April 2018 at 13:15,
On 4 April 2018 at 13:15, Ryan Schmidt wrote:
> On Apr 1, 2018, at 11:02, Perry E. Metzger wrote:
>
>> As some of you have noticed, I've been trying to keep the PR queue
>> relatively clear.
>
> Thanks very much for that!
Indeed. What you are doing is simply amazing.
>> Also, Mojca brought the
On Apr 1, 2018, at 11:02, Perry E. Metzger wrote:
> As some of you have noticed, I've been trying to keep the PR queue
> relatively clear.
Thanks very much for that!
> I'm wondering if we should therefore encourage people to submit github
> PRs if they have working patches (or are submitting