From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Norbert Lange <nolange79@gmail.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
gdb@sourceware.org, Gary Benson <gbenson@redhat.com>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: Automatically fetching Build ID from remote libraries and resole them locally?
Date: Mon, 6 Apr 2020 14:16:15 +0200 [thread overview]
Message-ID: <20200406121615.GA2380468@host1.jankratochvil.net> (raw)
In-Reply-To: <CADYdroM9eUJ9TCG829xR_-GbBk+Sfr9m3z4+XOkhydC7oRWqQw@mail.gmail.com>
On Mon, 06 Apr 2020 14:08:55 +0200, Norbert Lange wrote:
> How do I read the list at https://src.fedoraproject.org/rpms/gdb/tree/master.
> Are all patches applied, or are the ones starting with 'gdb-6.6' only
> for that version?
All of them are applied, in this order:
https://src.fedoraproject.org/rpms/gdb/blob/master/f/_patch_order
Although I would find it most easy to just use some Fedora virtual machine
(when you do not run Fedora natively).
> An a different note, I dont know if you are a GDB maintainer,
I am no longer.
> but the topic should be the upstream version?
This mailing list is sure about the upstream version. Just saying the problem
is solved in Fedora version so the patches could be somehow imported.
> It was not clear to me Redhat gdb and sourceware gdb are two different things.
(sourceware == FSF == upstream) != (Fedora == Red Hat; in this case)
Jan
next prev parent reply other threads:[~2020-04-06 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 14:20 Norbert Lange
2020-03-28 0:40 ` Frank Ch. Eigler
2020-03-30 8:35 ` Norbert Lange
2020-03-30 8:45 ` Jan Kratochvil
2020-03-30 9:04 ` Norbert Lange
2020-03-30 9:19 ` Jan Kratochvil
2020-03-30 18:43 ` Gary Benson
2020-04-06 11:31 ` Norbert Lange
2020-04-06 11:49 ` Jan Kratochvil
2020-04-06 12:08 ` Norbert Lange
2020-04-06 12:16 ` Jan Kratochvil [this message]
2020-04-06 12:53 ` Norbert Lange
2020-04-06 14:41 ` Norbert Lange
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=20200406121615.GA2380468@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=fche@redhat.com \
--cc=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=nolange79@gmail.com \
--cc=sergiodj@redhat.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).