From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: [26007] trunk/buildroot/package/openssl
Date: Tue, 14 Apr 2009 11:32:34 +1000 [thread overview]
Message-ID: <20090414013234.GA29812@cloud.net.au> (raw)
In-Reply-To: <20090407070120.F1F0D768C5@busybox.osuosl.org>
On Tue, Apr 07, 2009 at 07:01:20AM +0000, jacmet at uclibc.org wrote:
> Author: jacmet
> Date: 2009-04-07 07:01:20 +0000 (Tue, 07 Apr 2009)
> New Revision: 26007
>
> Log:
> openssl: bump version
>
> Patch by Gustavo Zacarias <gustavo@zacarias.com.ar>, closes #217
>
> Fixes multiple security flaws - See
> http://www.openssl.org/news/secadv_20090325.txt for details.
>
> Added:
> trunk/buildroot/package/openssl/openssl-0.9.8k-do-not-build-docs.patch
> trunk/buildroot/package/openssl/openssl-0.9.8k-dont-force-large-file.patch
> trunk/buildroot/package/openssl/openssl-0.9.8k-nofips.patch
> trunk/buildroot/package/openssl/openssl-0.9.8k-uclibc-susv3-legacy.patch
>
> Removed:
> trunk/buildroot/package/openssl/openssl-0.9.8j-do-not-build-docs.patch
> trunk/buildroot/package/openssl/openssl-0.9.8j-dont-force-large-file.patch
> trunk/buildroot/package/openssl/openssl-0.9.8j-nofips.patch
> trunk/buildroot/package/openssl/openssl-0.9.8j-uclibc-susv3-legacy.patch
>
> Modified:
> trunk/buildroot/package/openssl/openssl.mk
How about removing the version number from the patch filenames? They're just
making the upgrades messy and there doesn't seem to have any benefit.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2009-04-14 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 7:01 [Buildroot] svn commit: [26007] trunk/buildroot/package/openssl jacmet at uclibc.org
2009-04-14 1:32 ` Hamish Moffatt [this message]
2009-04-14 5:21 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090414013234.GA29812@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.