From: "Tulio Magno Quites Machado Filho" <tuliom@linux.vnet.ibm.com>
To: libc-stable@sourceware.org
Subject: Re: [COMMITTED 2.22] Handle overflow in __hcreate_r
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <878u33wasd.fsf@totoro.br.ibm.com> (raw)
In-Reply-To: <1454150677-7735-1-git-send-email-aurelien@aurel32.net> (Aurelien Jarno's message of "Sat, 30 Jan 2016 11:44:36 +0100")
Aurelien Jarno <aurelien@aurel32.net> writes:
> diff --git a/ChangeLog b/ChangeLog
> index 9740c89..e818995 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,8 @@
> +2015-08-25 Ondřej Bílka <neleai@seznam.cz>
Interesting... I noticed you kept the original date in the ChangeLog.
Should we update the date entry when backporting patches to stable branches?
--
Tulio Magno
next prev parent reply other threads:[~2016-02-02 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 Aurelien Jarno
2016-01-01 0:00 ` Tulio Magno Quites Machado Filho [this message]
2016-01-01 0:00 ` Mike Frysinger
2016-01-01 0:00 ` Tulio Magno Quites Machado Filho
2016-01-01 0:00 ` Mike Frysinger
2016-01-01 0:00 ` [COMMITTED 2.22] Improve check against integer wraparound in hcreate_r [BZ #18240] Aurelien Jarno
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=878u33wasd.fsf@totoro.br.ibm.com \
--to=tuliom@linux.vnet.ibm.com \
--cc=libc-stable@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).