From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: Contributor guidelines - Re: Ready for Write After Approval - Re: [PATCH v2] - Adapt to Python-3 print syntax
Date: Mon, 20 Oct 2025 05:25:50 +0300 [thread overview]
Message-ID: <86wm4qxqa9.fsf@gnu.org> (raw)
In-Reply-To: <874iruk8i1.fsf@jeremybryant.net> (message from Jeremy Bryant on Sun, 19 Oct 2025 20:16:06 +0100)
> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: tom@tromey.com, gdb-patches@sourceware.org
> Date: Sun, 19 Oct 2025 20:16:06 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I think you expect too much from the GDB maintenance processes. One
> > day is nowhere near enough to ping about approved-but-not-committed
> > changes.
>
> Eli, bringing back the second-part, truncated, of my message:-
>
> "
> PS:
> I'm not sure about the etiquette for following-up but presumably it's
> soon after approval so the patch is still applicable to master.
>
> The guidance here says one week for patch review only
> https://sourceware.org/gdb/wiki/ContributionChecklist
> "
>
>
> Perhaps my request wasn't worded properly. What is a typical wait time
> that is appropriate?
A week at least, IME.
> To edit the file at
> https://sourceware.org/gdb/wiki/ContributionChecklist,
> do we submit ideas or patches here or in some other way?
I don't know, sorry.
next prev parent reply other threads:[~2025-10-20 2:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 22:14 [PATCH] " Jeremy Bryant
2025-10-15 12:01 ` Eli Zaretskii
2025-10-15 13:44 ` Tom Tromey
2025-10-15 20:19 ` [PATCH v2] " Jeremy Bryant
2025-10-15 20:32 ` Tom Tromey
2025-10-16 20:04 ` Ready for Write After Approval - " Jeremy Bryant
2025-10-17 11:25 ` Eli Zaretskii
2025-10-19 19:16 ` Contributor guidelines - " Jeremy Bryant
2025-10-20 2:25 ` Eli Zaretskii [this message]
2025-10-17 14:45 ` Tom Tromey
2025-10-19 17:02 ` Thank you - " Jeremy Bryant
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=86wm4qxqa9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jb@jeremybryant.net \
--cc=tom@tromey.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