From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] (e)glibc: add security patches for CVE-2014-7817
Date: Thu, 27 Nov 2014 14:57:09 -0300 [thread overview]
Message-ID: <547765F5.4080402@zacarias.com.ar> (raw)
In-Reply-To: <20141127174959.GB4690@tarshish>
On 11/27/2014 02:49 PM, Baruch Siach wrote:
> Embargoed? Really?
>
> Anyway, I'm not sure leaving this comment here makes sense.
It was not so long ago :)
I try to keep patches as pristine as possible, just adding the SoB or
any relevant comment above.
We can get rid of that, but i don't think it will make any difference.
Regards.
next prev parent reply other threads:[~2014-11-27 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 15:19 [Buildroot] [PATCH] (e)glibc: add security patches for CVE-2014-7817 Gustavo Zacarias
2014-11-27 17:49 ` Baruch Siach
2014-11-27 17:57 ` Gustavo Zacarias [this message]
2014-11-27 22:25 ` 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=547765F5.4080402@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox