From: Aaron Merey <amerey@redhat.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [heads up] GDB 11.2 "respin" release next weekend (Jan 15-16)
Date: Thu, 13 Jan 2022 11:48:03 -0500 [thread overview]
Message-ID: <CAJDtP-STuCuPxJCb55aV_dcAWXBUMz+7YqE8=3bJtkRcogJe-g@mail.gmail.com> (raw)
In-Reply-To: <20220113104910.GV622389@redhat.com>
On Wed, Jan 12, 2022 at 10:58 PM Joel Brobecker <brobecker@adacore.com> wrote:
> With that said, unless the patch you are proposing has been deployed
> and in real-world use for a while, my experience tells me that it is
> a really risky proposition to be pushing a patch like that at the very
> last minute. On the surface, the patch looks OK, and it's contained
> within the download side of debuginfod, but we could imagine a bug
> in this patch causing debuginfod downloads to crash, thus rendering
> the entire feature no longer usable. When we are in the last stretches
> of the preparation of a release which is going to be the last release
> from this branch, unless the fix is absolutely critical or obviously
> safe, my personal approach has been to remember that the .2 release
> is first and foremost a corrective release. Just my 2 cents.
On Thu, Jan 13, 2022 at 5:49 AM Andrew Burgess <aburgess@redhat.com> wrote:
> I agree with Joel, this isn't a bug fix, so I don't think it's
> appropriate to include in 11.2.
Fair points. To be safe let's not rush my patch then.
Thanks,
Aaron
next prev parent reply other threads:[~2022-01-13 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 8:27 Joel Brobecker
2022-01-12 22:29 ` Aaron Merey
2022-01-13 3:58 ` Joel Brobecker
2022-01-13 10:49 ` Andrew Burgess
2022-01-13 16:48 ` Aaron Merey [this message]
2022-01-11 23:16 Simon Sobisch
2022-01-12 5:12 ` Joel Brobecker
2022-01-12 6:03 ` Tom Tromey
2022-01-12 10:41 ` Andrew Burgess
2022-01-12 10:59 ` Joel Brobecker
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='CAJDtP-STuCuPxJCb55aV_dcAWXBUMz+7YqE8=3bJtkRcogJe-g@mail.gmail.com' \
--to=amerey@redhat.com \
--cc=aburgess@redhat.com \
--cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).