[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Bryan Stansell bryan@conserver.com
Fri, 29 May 2015 14:58:06 GMT
Yep, going through all the reports/patches/posts since the last release is part of the plan. The break list patch will be included. If you have the username/peername "stable", send it along, otherwise we can try and work it in when you're comfortable with it. Is the peername the result of getpeername(), or more a remote username like from SO_PEERCRED? I just ask because the latter is less portable. Thanks. Bryan > On May 29, 2015, at 12:25 AM, Artem Savkov <asavkov@redhat.com> wrote: > > Are there plans to include the breaksequence patch ([1])? > I also have another one that adds CONSERVER_USERNAME and > CONSERVER_PEERNAME variables to task's environment. It's a simple patch, > but I don't think it went through proper testing just yet. > Would that be something that can be merged as well? > > 1. https://www.conserver.com/pipermail/users/2015-March/msg00000.html > > -- > Regards, > Artem >