From: Luis Machado via Gdb <gdb@sourceware.org>
To: Simon Marchi <simark@simark.ca>,
Bruno Larsen <blarsen@redhat.com>,
gdb@sourceware.org
Subject: Re: Proposal: Add review tags to patch review workflow.
Date: Mon, 10 Oct 2022 10:39:17 +0100 [thread overview]
Message-ID: <965ebd9e-796f-ad48-13b6-b5d6298eef23@arm.com> (raw)
In-Reply-To: <754258e5-b9b7-0785-5580-f8f54e7ad6ad@simark.ca>
Hi Simon,
On 10/7/22 21:46, Simon Marchi via Gdb wrote:
>
>
> On 2022-10-07 03:49, Bruno Larsen via Gdb wrote:
>> It's been over a week since the last response of this proposal, and all responses have been positive. Does this mean the proposal is accepted? There aren't any guidelines about proposals in the wiki, so I'm a bit lost here.
>>
>
> We don't really have a formal process for voting / adopting proposals
> like this. Given there was no negative feedback at all (from what I
> remember), please go ahead and update the wiki. I will try to remember
> to use the tags from now on.
>
> Simon
Bruno can correct me if I'm wrong, but I think what us contributors are looking for is some sort of message from global maintainers
stating this is acceptable and we should move forward. Even better if the global maintainers can discuss this between
themselves and provide feedback to the rest of the contributors.
Without any formal position, it is unclear whether one should proceed with some proposal/improvement or not.
Does that sound reasonable?
prev parent reply other threads:[~2022-10-10 9:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 11:04 Bruno Larsen via Gdb
2022-09-25 22:38 ` Lancelot SIX via Gdb
2022-09-26 13:55 ` Simon Marchi via Gdb
2022-09-26 16:42 ` Joel Brobecker via Gdb
2022-09-27 8:39 ` Luis Machado via Gdb
2022-09-27 8:42 ` Luis Machado via Gdb
2022-09-27 9:38 ` Lancelot SIX via Gdb
2022-09-27 21:07 ` Thiago Jung Bauermann via Gdb
2022-09-26 21:32 ` John Baldwin
2022-09-27 8:06 ` Bruno Larsen via Gdb
2022-09-27 12:02 ` Simon Marchi via Gdb
2022-09-27 12:03 ` Bruno Larsen via Gdb
2022-09-27 17:11 ` John Baldwin
2022-09-27 7:58 ` Bruno Larsen via Gdb
2022-09-27 12:03 ` Simon Marchi via Gdb
2022-09-26 15:59 ` Luis Machado via Gdb
2022-09-26 16:32 ` Elena Zannoni via Gdb
2022-09-27 8:30 ` Bruno Larsen via Gdb
2022-09-27 20:50 ` Thomas Schwinge
2022-10-07 7:49 ` Bruno Larsen via Gdb
2022-10-07 20:46 ` Simon Marchi via Gdb
2022-10-08 6:23 ` Eli Zaretskii via Gdb
2022-10-08 11:55 ` Simon Marchi via Gdb
2022-10-08 12:44 ` Eli Zaretskii via Gdb
2022-10-09 0:29 ` Simon Marchi via Gdb
2022-10-10 9:27 ` Bruno Larsen via Gdb
2022-10-10 9:47 ` Eli Zaretskii via Gdb
2022-10-10 10:11 ` Bruno Larsen via Gdb
2022-10-10 11:27 ` Eli Zaretskii via Gdb
2022-10-10 12:31 ` Bruno Larsen via Gdb
2022-10-10 13:14 ` Eli Zaretskii via Gdb
2022-10-10 13:26 ` Bruno Larsen via Gdb
2022-10-10 15:25 ` Eli Zaretskii via Gdb
2022-10-10 13:34 ` Pedro Alves
2022-10-10 9:39 ` Luis Machado via Gdb [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=965ebd9e-796f-ad48-13b6-b5d6298eef23@arm.com \
--to=gdb@sourceware.org \
--cc=blarsen@redhat.com \
--cc=luis.machado@arm.com \
--cc=simark@simark.ca \
/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