Stephen Warren <[EMAIL PROTECTED]> writes:

> It's done. I was a little hesitant to keep dumping everything into
> SVN, in case any buggy SSL code ever prevented a release. Still, I
> guess it's easily disabled by simply removing the command-line
> options (assuming the integration into the rest of the code didn't
> break plain-text!)

You should probably test plain-text every once in a while since it's
so easy to do, but don't worry about buggy code in SVN. There's no
pressing need for a new release, and if there was, I'm sure SVN allows
me to tag a branch mixing an older revision of tmda-ofmipd with the
latest revision of all the other files, etc.

> Re: tlslite. I wonder if I should make a tlslite-0.3.8-sw tarball, to
> make it easier for people to get all my changes.

I'd only consider that as a last resort. First I'd press the tlslite
maintainer to integrate your changes and cut a release. That way,
people can install it through their OS's automated packaging method
rather than having to deal with a rogue tarball.

_________________________________________________
tmda-workers mailing list ([email protected])
http://tmda.net/lists/listinfo/tmda-workers

Reply via email to