Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I don't :-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission?
On 9 January 2014 22:26, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I don't :-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission?
I suspect Ron Teitelbaum holds the keys.
frank
Frank Shearar Sent: Thursday, January 09, 2014 5:54 PM
On 9 January 2014 22:26, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I don't
:-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission?
I suspect Ron Teitelbaum holds the keys.
Actually I don't have write access to that repo. It's just Andreas. We could create a new repo or maybe have someone add Eliot (or me) to the squeaksource SqueakSSL repo?
Ron Teitelbaum
On 10 January 2014 04:40, Ron Teitelbaum ron@usmedrec.com wrote:
Frank Shearar Sent: Thursday, January 09, 2014 5:54 PM
On 9 January 2014 22:26, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I don't
:-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission?
I suspect Ron Teitelbaum holds the keys.
Actually I don't have write access to that repo. It's just Andreas. We could create a new repo or maybe have someone add Eliot (or me) to the squeaksource SqueakSSL repo?
Oh, OK. Or we could ask an admin to do that. David, you have admin rights, don't you?
frank
Ron Teitelbaum
In this case I wonder if it might make more sense to move the plugin into the VMMaker repository. The SqueakSSLPlugin is complete and it seems unlikely to need any active development aside from minor updates such as the one Eliot is posting here.
Normally I would discourage moving plugins into VMMaker if they are part of any active project, but this seems like a case it which in which a separate repository is not needed, and it may be easier for everyone to give it a home along with the other stable plugins.
Eliot, is that OK with you?
Sorry for top posting, I'm stuck on an ancient web browser for the moment.
Dave
On 10 January 2014 04:40, Ron Teitelbaum ron@usmedrec.com wrote:
Frank Shearar Sent: Thursday, January 09, 2014 5:54 PM
On 9 January 2014 22:26, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I
don't :-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission?
I suspect Ron Teitelbaum holds the keys.
Actually I don't have write access to that repo. It's just Andreas. We could create a new repo or maybe have someone add Eliot (or me) to the squeaksource SqueakSSL repo?
Oh, OK. Or we could ask an admin to do that. David, you have admin rights, don't you?
frank
Ron Teitelbaum
On Fri, Jan 10, 2014 at 9:45 AM, David T. Lewis lewis@mail.msen.com wrote:
In this case I wonder if it might make more sense to move the plugin into the VMMaker repository. The SqueakSSLPlugin is complete and it seems unlikely to need any active development aside from minor updates such as the one Eliot is posting here.
Normally I would discourage moving plugins into VMMaker if they are part of any active project, but this seems like a case it which in which a separate repository is not needed, and it may be easier for everyone to give it a home along with the other stable plugins.
Eliot, is that OK with you?
Yes, that's fine with me.
Sorry for top posting, I'm stuck on an ancient web browser for the moment.
lot's more contexts where top-posting seems acceptable to me these days; e.g. phones.
Dave
On 10 January 2014 04:40, Ron Teitelbaum ron@usmedrec.com wrote:
Frank Shearar Sent: Thursday, January 09, 2014 5:54 PM
On 9 January 2014 22:26, Eliot Miranda eliot.miranda@gmail.com
wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL?
I
don't :-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission?
I suspect Ron Teitelbaum holds the keys.
Actually I don't have write access to that repo. It's just Andreas. We could create a new repo or maybe have someone add Eliot (or me) to the squeaksource SqueakSSL repo?
Oh, OK. Or we could ask an admin to do that. David, you have admin rights, don't you?
frank
Ron Teitelbaum
On Fri, Jan 10, 2014 at 10:30:47AM -0800, Eliot Miranda wrote:
On Fri, Jan 10, 2014 at 9:45 AM, David T. Lewis lewis@mail.msen.com wrote:
In this case I wonder if it might make more sense to move the plugin into the VMMaker repository. The SqueakSSLPlugin is complete and it seems unlikely to need any active development aside from minor updates such as the one Eliot is posting here.
Normally I would discourage moving plugins into VMMaker if they are part of any active project, but this seems like a case it which in which a separate repository is not needed, and it may be easier for everyone to give it a home along with the other stable plugins.
Eliot, is that OK with you?
Yes, that's fine with me.
Done.
Thank you Andreas.
Dave
Eliot, can you please describe briefly what sort of changes you do revising these plugins, just to keep me in course?
On 9 January 2014 23:26, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I
don't :-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission? -- TIA, Eliot
Hi Igor,
On Fri, Jan 10, 2014 at 10:51 AM, Igor Stasenko siguctua@gmail.com wrote:
Eliot, can you please describe briefly what sort of changes you do revising these plugins, just to keep me in course?
In this case I just applied the script that changes the meta-information such as export:, inline:, var:type: et al from the old send form to the "new" pragma form. e.g.
primitiveAccept "Primitive. Starts or continues a server handshake using the current session. Will eventually produce output to be sent to the client. Requires the host and cert name to be set for the session. Returns a code indicating the sate of the connection:
0 - Number of bytes to be sent to the client.
0 - Success. The connection is established. -1 - More input is required. < -1 - Other errors. " | start srcLen dstLen srcOop dstOop handle srcPtr dstPtr result | self var: #srcPtr type: 'char *'. self var: #dstPtr type: 'char *'. self export: true. ... => primitiveAccept "Primitive. Starts or continues a server handshake using the current session. Will eventually produce output to be sent to the client. Requires the host and cert name to be set for the session. Returns a code indicating the sate of the connection:
0 - Number of bytes to be sent to the client.
0 - Success. The connection is established. -1 - More input is required. < -1 - Other errors. " | start srcLen dstLen srcOop dstOop handle srcPtr dstPtr result | <var: #srcPtr type: 'char *'> <var: #dstPtr type: 'char *'> <export: true> ...
On 9 January 2014 23:26, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I
don't :-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission? -- TIA, Eliot
-- Best regards, Igor Stasenko.
On 10 January 2014 20:06, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Igor,
On Fri, Jan 10, 2014 at 10:51 AM, Igor Stasenko siguctua@gmail.comwrote:
Eliot, can you please describe briefly what sort of changes you do revising these plugins, just to keep me in course?
In this case I just applied the script that changes the meta-information such as export:, inline:, var:type: et al from the old send form to the "new" pragma form. e.g.
primitiveAccept "Primitive. Starts or continues a server handshake using the current session. Will eventually produce output to be sent to the client. Requires the host and cert name to be set for the session. Returns a code indicating the sate of the connection:
0 - Number of bytes to be sent to the client.
0 - Success. The connection is established. -1 - More input is required. < -1 - Other errors. " | start srcLen dstLen srcOop dstOop handle srcPtr dstPtr result | self var: #srcPtr type: 'char *'. self var: #dstPtr type: 'char *'. self export: true. ... => primitiveAccept "Primitive. Starts or continues a server handshake using the current session. Will eventually produce output to be sent to the client. Requires the host and cert name to be set for the session. Returns a code indicating the sate of the connection:
0 - Number of bytes to be sent to the client.
0 - Success. The connection is established. -1 - More input is required. < -1 - Other errors. " | start srcLen dstLen srcOop dstOop handle srcPtr dstPtr result | <var: #srcPtr type: 'char *'> <var: #dstPtr type: 'char *'> <export: true> ...
Thanks :)
On 9 January 2014 23:26, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
who has write rights to http://www.squeaksource.com/SqueakSSL? I
don't :-(. Here's a pragmatized version of the plugin. Can someone either put it in place and/or give me write permission? -- TIA, Eliot
-- Best regards, Igor Stasenko.
-- best, Eliot
vm-dev@lists.squeakfoundation.org