-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL versions 1.0.2d and 1.0.1p.
These releases will be made available on 9th July. They will fix a
single
On Wed, Mar 18, 2015 at 5:14 AM, Matt Caswell m...@openssl.org wrote:
On 18/03/15 07:59, Jakob Bohm wrote:
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would
I just posted an updated version of my script in a new
thread, titled
Minimizing the pain of reformatting your OpenSSL patches
Regards,
msp
On 03/19/2015 02:22 AM, Dr. Matthias St. Pierre wrote:
Hello,
Here is a recipe to guide you through the reformatting.
It worked nicely for me. I
On 18/03/2015 10:14, Matt Caswell wrote:
On 18/03/15 07:59, Jakob Bohm wrote:
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming
On 18/03/15 07:59, Jakob Bohm wrote:
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL versions 1.0.2a,
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL versions 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf.
These releases
On 18/03/15 10:45, Jakob Bohm wrote:
However the patch rebasing instructions are *completely
useless* for those of us whomaintain private patches
against releases tarballs. We *don't* have any of this
in a clone of your gitand we *have no way* to access
intermediary git steps from your
We maintain our own derivative of OpenSSL and haven't had any
significant issues due to the code reformat. We simply run the reformat
script on our downstream derivative. We can then generate patch files
of our changes and reapply them to new OpenSSL releases. It was fairly
straight forward.
Nice, so the extra work is minimal for complete forks of
OpenSSL.
The extra work is also documented (in a place not linked from
the wiki) for those who maintain a git fork of the OpenSSL
repository.
But I have not yet seen a meaningful recipe for those of us
who maintain a traditional set of
The extra work is also documented (in a place not linked from the wiki) for
those who maintain a git fork of the OpenSSL repository.
I just tossed together https://wiki.openssl.org/index.php/Code_reformatting
Found off the main page,
Thanks for the three line upgracde recipe in
https://wiki.openssl.org/index.php/Code_reformatting
It's as simple as you stated, indeed.
The reformatting was a good thing to do. Also, it makes sense to me to apply it
to all
stable branches uniformly, in order to simplify cross-branch merging.
: Re: [openssl-users] [openssl-announce] Forthcoming OpenSSL releases
Nice, so the extra work is minimal for complete forks of OpenSSL.
The extra work is also documented (in a place not linked from the wiki) for
those who maintain a git fork of the OpenSSL repository.
But I have not yet seen
12 matches
Mail list logo
