public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>,
	"Frank Ch. Eigler" <fche@redhat.com>
Cc: Japin Li <japinli@hotmail.com>
Subject: Re: Request a Sourceware Bugzilla account for reporting bug
Date: Thu, 26 May 2022 17:02:45 -0400	[thread overview]
Message-ID: <8ca670e6-019f-16b9-63e6-9b442ce49454@redhat.com> (raw)
In-Reply-To: <MEYP282MB166917EAE0D169D431DC8FF3B6D69@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM>

On 5/24/22 21:02, Japin Li via Overseers wrote:
> 
> On Tue, 24 May 2022 at 18:51, Frank Ch. Eigler <fche@redhat.com> wrote:
>> Hi -
>>
>>> I want to report a bug about GDB, however, I cannot register the account
>>> through the web interface [1].  Please help me out, Thanks in advance!
>>> [1] https://sourceware.org/bugzilla/createaccount.cgi
>>
>> Account created, welcome.
>>
> 
> Thank you! After some search, I found the bug is in GDB 8.1.1 and fixed in
> GDB 12 [1].  I want to know why this doestn't backpatch to where it occurs?

I suggest asking that question to the gdb maintainers.

Please see their mailing lists here:
https://www.sourceware.org/gdb/mailing-lists/

> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=23613
 
An older release branch may be closed to limit the cost of maintenance,
and so bugs are not always backported to all the old branches.

-- 
Cheers,
Carlos.


      reply	other threads:[~2022-05-26 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 10:39 Japin Li
2022-05-24 10:51 ` Frank Ch. Eigler
2022-05-25  1:02   ` Japin Li
2022-05-26 21:02     ` Carlos O'Donell [this message]

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=8ca670e6-019f-16b9-63e6-9b442ce49454@redhat.com \
    --to=carlos@redhat.com \
    --cc=fche@redhat.com \
    --cc=japinli@hotmail.com \
    --cc=overseers@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).