From: Nick Clifton <nickc@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>,
Simon Marchi <simon.marchi@efficios.com>,
gti-tac@lists.linuxfoundation.org
Subject: Re: CY23 - Status of service enumeration.
Date: Tue, 7 Feb 2023 12:55:41 +0000 [thread overview]
Message-ID: <5e2916df-018d-e591-4301-910c0ac269d1@redhat.com> (raw)
In-Reply-To: <4718eb70-b843-0f46-9555-cbba58f70713@redhat.com>
Hi Carlos,
>>> Is binutils going to be any different from gdb?
>> I don't know about the binutils process. Perhaps we can ask Nick
>> Clifton to review our list for GDB and complement it with any
>> information specific for binutils?
It is basically the same. We use the same git repository as GDB,
the same bugzilla and buildbot systems and the same website hosting.
There are a few discrepancies however:
* The website contents are not generated by scripts, instead
they are hand made. The documentation parts of the binutils
web site are created by building the docs locally and then
uploading to the site.
* We are not using patchwork at the moment. Given the relatively
light patch review load for the binutils, it may never be used.
* We do not currently have daily snapshots of the binutils sources
although these used to happen in the (long distant) past.
* Not quite as many mailing lists as GDB, but basically similar.
Do you want a full list similar to the one produced by Simon and Joel
or is this discrepancy information sufficient ?
Cheers
Nick
next prev parent reply other threads:[~2023-02-07 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 17:35 CY23 - Status of service enumeration Carlos O'Donell
2023-02-06 19:11 ` Simon Marchi
2023-02-06 22:09 ` Carlos O'Donell
2023-02-07 12:55 ` Nick Clifton [this message]
2023-02-07 13:55 ` Carlos O'Donell
2023-02-07 14:41 ` Nick Clifton
2023-02-07 17:25 ` Carlos O'Donell
2023-02-08 13:42 ` Nick Clifton
2023-02-06 22:36 ` Joseph Myers
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=5e2916df-018d-e591-4301-910c0ac269d1@redhat.com \
--to=nickc@redhat.com \
--cc=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.org \
--cc=simon.marchi@efficios.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).