Sussman also wanted me to work on this neon branch to revamp the SSL
support. Should that be indicated in the COMMITTERS file? (as long as
you are in there...)
Sergey A. Lipnevich wrote:
> Yes. I mentioned to Ben that I don't have commit privilege, but this
> was in the issue so I guess it didn't reach the target :-)... I have a
> patch that combines MBK work with some more obvious fixing, now I'm up
> against harder part, things like I sent to the list recently. The plan
> is perfect for me, I'm determined to complete this task, albeit I'm
> moving slowly because of lack of UNIX development experience. I'll
> contact you separately about the account.
> Thank you!
> firstname.lastname@example.org wrote:
>>"Sergey A. Lipnevich" <email@example.com> wrote to Mike Pilato:
>>>Sure, thank you :-)! That's precisely the reason: NE_XML_INVALID
>>>became NE_XML_ABORT in Neon 0.24 without changing the value (-1), and
>>>return value contract has changed for startelm callback
>>>(NE_XML_DECLINE is now 0 instead of -2). And there's no validate
>>>callback anymore, but that's another story...
>>Sergey, just to make sure we're working toward the same goal here: Ben
>>Collins-Sussman created this branch for you
>>I think the idea is that first we -- uh, you -- get Neon 0.24 working
>>on the branch, then David Waite and you together get cert support
>>working on the branch (since by itself, the upgrade to Neon 0.24 is
>>expected to break certificates in Subversion).
>>Then we fold the branch back into trunk.
>>I'm aware that neither you nor David Waite have promised that all this
>>will happen :-), so this mail is really a question: does this plan
>>sound good to you guys?
>>If it does, mail me your tigris username and a password of your choice
>>(plain text or crypted is fine), and I'll set you up with commit
>>access on that branch.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Aug 5 20:22:40 2003