From: Luis Machado <luis.machado@arm.com>
To: Pedro Alves <pedro@palves.net>, gdb@sourceware.org
Subject: Re: GDB BoF Agenda for GNU Cauldron 2022?
Date: Tue, 13 Sep 2022 11:48:03 +0100 [thread overview]
Message-ID: <a9890cab-ed7d-467d-b13c-187be59c98f1@arm.com> (raw)
In-Reply-To: <a85a4f7c-43d5-9631-2944-60ad4f96478c@arm.com>
On 9/12/22 17:24, Luis Machado wrote:
> Hi,
>
> On 9/12/22 16:43, Pedro Alves wrote:
>> Hi!
>>
>> Once again, we'll have a gdb BoF session in the Cauldron this year:
>>
>> https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.the_gdb_bof
>>
>> As in previous years, the intention is to discuss whatever gdb-related topics people feel like
>> needs discussing, hence no agenda listed in the schedule (I didn't have a list of topics in mind
>> when I proposed the slot). As before, I intend to collect topics of interest at the start of the
>> session, and then try to cover them all. That seems to have worked OK in the past.
>>
>> However, if anyone has topics they already know they'd like to see brought up, please feel
>> free to let me know in advance.
>>
>> Hope to see you there!
>>
>> Cheers,
>> Pedro Alves
>
> One topic GDB developers might be interested in (but feel free to skip it otherwise), is patch reviewing.
>
> - Timing
>
> Everyone's busy schedules aside, is there a way to improve the time it takes for patches to get reviewed? Do we need to seek
> (to appoint) more maintainers?
>
> - Tracking
>
> Is there a better patch-tracking system so contributions don't get forgotten (better than pinging patches once a week).
>
> It would be nice to have a clear list of contributions waiting to be reviewed, as opposed to having to go through mailing
> list entries.
>
> - Pre-commit testing
>
> Some sort of infrastructure that just build-tests the patch/series to hopefully speed-up reviewing. Possibly using our current
> sourceware buildbot infrastructure?
>
> Regards,
> Luis
Sorry, remembered another one:
- Discuss adopting an auto-formatting tool for source code in the future (clang-format?), so developers/reviewers
don't need to spend time spotting such things. The experience with python black has been nice.
next prev parent reply other threads:[~2022-09-13 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 15:43 Pedro Alves
2022-09-12 16:24 ` Luis Machado
2022-09-13 10:48 ` Luis Machado [this message]
2022-09-13 11:02 ` Tom Kacvinsky
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=a9890cab-ed7d-467d-b13c-187be59c98f1@arm.com \
--to=luis.machado@arm.com \
--cc=gdb@sourceware.org \
--cc=pedro@palves.net \
/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).