From: Mike Frysinger <vapier@gentoo.org>
To: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Cc: 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: <20160202180623.GG7732@vapier.lan> (raw)
In-Reply-To: <87d1sfrokv.fsf@totoro.br.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On 02 Feb 2016 15:48, Tulio Magno Quites Machado Filho wrote:
> Mike Frysinger <vapier@gentoo.org> writes:
> > On 02 Feb 2016 10:34, Tulio Magno Quites Machado Filho wrote:
> >> 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?
> >
> > i think a lot of us have because cherry-pick does it for us.
>
> Have updated the ChangeLog date?
> If so, what is the magic you've done to let cherry-pick do that?
> I always change that by hand.
check out:
https://sourceware.org/glibc/wiki/GlibcGit#ChangeLog
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-02 18:06 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
2016-01-01 0:00 ` Mike Frysinger
2016-01-01 0:00 ` Tulio Magno Quites Machado Filho
2016-01-01 0:00 ` Mike Frysinger [this message]
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=20160202180623.GG7732@vapier.lan \
--to=vapier@gentoo.org \
--cc=libc-stable@sourceware.org \
--cc=tuliom@linux.vnet.ibm.com \
/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).