On Sat, Sep 22, 2018 at 11:41:05AM -0700, Geoff Hill wrote:
> New patch included.
>
> On Sat, Sep 22, 2018 at 07:09:44AM +0100, Jason McIntyre wrote:
> > does the "ok" request mean you have commit access? (sorry, find it hard
> > to keep track)
>
> Nope, no commit access, just a user sending up
ok nicm
On Sat, Sep 22, 2018 at 10:15:21AM +0200, Anton Lindqvist wrote:
> On Fri, Sep 21, 2018 at 06:36:54PM -0700, Geoff Hill wrote:
> > Hello tech,
> >
> > I noticed the event(3) manual pages don't mention the
> > bufferevent_setwatermark(3) function and glosses over the details of
> >
New patch included.
On Sat, Sep 22, 2018 at 07:09:44AM +0100, Jason McIntyre wrote:
> does the "ok" request mean you have commit access? (sorry, find it hard
> to keep track)
Nope, no commit access, just a user sending up a documentation fix.
> regarding the markup: there is no need to quote
On Sat, Sep 22, 2018 at 10:15:21AM +0200, Anton Lindqvist wrote:
> On Fri, Sep 21, 2018 at 06:36:54PM -0700, Geoff Hill wrote:
> > Hello tech,
> >
> > I noticed the event(3) manual pages don't mention the
> > bufferevent_setwatermark(3) function and glosses over the details of
> > watermarks,
On Fri, Sep 21, 2018 at 06:36:54PM -0700, Geoff Hill wrote:
> Hello tech,
>
> I noticed the event(3) manual pages don't mention the
> bufferevent_setwatermark(3) function and glosses over the details of
> watermarks, even though there's a few programs in userland that set both
> read and write
Hello tech,
I noticed the event(3) manual pages don't mention the
bufferevent_setwatermark(3) function and glosses over the details of
watermarks, even though there's a few programs in userland that set both
read and write watermarks. Looks like there was an effort in 2017
to add some
