> On 30 Jun 2016, at 08:28, Kurt Jaeger wrote:
>
> Hi!
>
>> I've got several patches pending for the www/node* ports [...]
>
>> I'd appreciate help from a willing and able committer to get these
>> in the tree, ideally before the next quarterly branch is cut.
>
> Done.
Thanks, Kurt. I apprec
Hi!
> I've got several patches pending for the www/node* ports [...]
> I'd appreciate help from a willing and able committer to get these
> in the tree, ideally before the next quarterly branch is cut.
Done.
--
p...@opsec.eu+49 171 3101372 4 years to go !
__
Howdy!
I've got several patches pending for the www/node* ports (I'm the maintainer
for these ports). One is a fix for several build failures that have been
recently reported, one is to fix portlint warnings, and the others are version
bumps to address security issues.
Build fix:
https://bugs.
On 5 May, Kevin Oberman wrote:
> On Thu, May 5, 2016 at 2:16 PM, Don Lewis wrote:
>
>> On 5 May, Kurt Jaeger wrote:
>> > Hi!
>> >
>> > One thing: There are issues with buildlogs attached to PR due
>> > to them blowing up the database of bugzilla. If all is fine,
>> > it's OK to just list the ar
On Thu, May 5, 2016 at 2:16 PM, Don Lewis wrote:
> On 5 May, Kurt Jaeger wrote:
> > Hi!
> >
> > One thing: There are issues with buildlogs attached to PR due
> > to them blowing up the database of bugzilla. If all is fine,
> > it's OK to just list the architectures tested. Second best
> > is put
On 5 May, Kurt Jaeger wrote:
> Hi!
>
> One thing: There are issues with buildlogs attached to PR due
> to them blowing up the database of bugzilla. If all is fine,
> it's OK to just list the architectures tested. Second best
> is putting broken buildlogs on some external site and put the link
> i
> On 05 May 2016, at 15:47, Kurt Jaeger wrote:
>
> Hi!
>
>> I've got a few PRs up that are ready for a willing and able committer:
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209214
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209215
>> https://bugs.freebsd.org/bugzilla/sho
Hi!
> I've got a few PRs up that are ready for a willing and able committer:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209214
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209215
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209216
Here's for the willing. The 'able' is st
Hi!
One thing: There are issues with buildlogs attached to PR due
to them blowing up the database of bugzilla. If all is fine,
it's OK to just list the architectures tested. Second best
is putting broken buildlogs on some external site and put the link
in the PR. Third is adding broken buildlogs a
Hi!
> > I've got a few PRs up that are ready for a willing and able committer:
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209214
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209215
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209216
>
> If you say what port(s) the
> On 5. mai 2016, at 00.49, Greg 'groggy' Lehey wrote:
>
>> On Wednesday, 4 May 2016 at 7:34:40 +0200, Bradley T. Hughes wrote:
>> Howdy!
>>
>> I've got a few PRs up that are ready for a willing and able committer:
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209214
>> https://bug
On Wednesday, 4 May 2016 at 7:34:40 +0200, Bradley T. Hughes wrote:
> Howdy!
>
> I've got a few PRs up that are ready for a willing and able committer:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209214
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209215
> https://bugs.freebsd.or
Howdy!
I've got a few PRs up that are ready for a willing and able committer:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209214
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209215
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209216
--
Bradley T. Hughes
bradleythug...@fastmail.
13 matches
Mail list logo