Re: [NEW] benchmarks/wrk

2018-04-24 Thread Jeremie Courreges-Anglas
On Tue, Apr 24 2018, Frederic Cambus wrote: > On Tue, Apr 24, 2018 at 10:35:20AM +0200, Jeremie Courreges-Anglas wrote: > >> > I'm aware that we are not supposed to import ports using GH_TAGNAME, I >> > opened an issue asking for a proper release tarball but I haven't got >> >

Re: [NEW] benchmarks/wrk

2018-04-24 Thread Frederic Cambus
On Tue, Apr 24, 2018 at 10:35:20AM +0200, Jeremie Courreges-Anglas wrote: > > I'm aware that we are not supposed to import ports using GH_TAGNAME, I > > opened an issue asking for a proper release tarball but I haven't got > > any feedback from upstream yet. I can host the tarball on distfiles.pl

Re: [NEW] benchmarks/wrk

2018-04-24 Thread Jeremie Courreges-Anglas
On Tue, Apr 24 2018, Stuart Henderson wrote: > On 2018/04/24 10:35, Jeremie Courreges-Anglas wrote: >> On Mon, Apr 23 2018, Frederic Cambus wrote: >> > Hi ports@, >> > >> > Here is a new port: benchmarks/wrk >> > >> > I'm aware that we are not supposed to

Re: [NEW] benchmarks/wrk

2018-04-24 Thread Stuart Henderson
On 2018/04/24 10:35, Jeremie Courreges-Anglas wrote: > On Mon, Apr 23 2018, Frederic Cambus wrote: > > Hi ports@, > > > > Here is a new port: benchmarks/wrk > > > > I'm aware that we are not supposed to import ports using GH_TAGNAME, I > > opened an issue asking for a proper

Re: [NEW] benchmarks/wrk

2018-04-24 Thread Jeremie Courreges-Anglas
On Mon, Apr 23 2018, Frederic Cambus wrote: > Hi ports@, > > Here is a new port: benchmarks/wrk > > I'm aware that we are not supposed to import ports using GH_TAGNAME, I > opened an issue asking for a proper release tarball but I haven't got > any feedback from upstream yet. I