From: krokus <nomadbyte@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Undefined behavior reported in copy_bitwise
Date: Fri, 10 Apr 2020 15:56:54 -0500 [thread overview]
Message-ID: <CAMCMYR73rOUD6bXUNKm_mU9=SN-iRS6OV+b2o1MrAMt-GEaQYA@mail.gmail.com> (raw)
In-Reply-To: <2ea2b4f7-b9f2-99c4-b301-e35d9f265690@simark.ca>
Simon,
> Could you please provide a ChangeLog entry for this, with the name and
> email address you'd like to have in there?
Will do.
Do I need to update the ChangeLog myself or you could do this with my entry?
I'm not set up for repo commit access.
next prev parent reply other threads:[~2020-04-10 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 23:50 krokus
2020-04-10 14:59 ` Simon Marchi
2020-04-10 20:56 ` krokus [this message]
2020-04-10 21:24 ` Simon Marchi
2020-04-11 1:08 ` Simon Marchi
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='CAMCMYR73rOUD6bXUNKm_mU9=SN-iRS6OV+b2o1MrAMt-GEaQYA@mail.gmail.com' \
--to=nomadbyte@gmail.com \
--cc=gdb-patches@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