On Wed, Jun 18, 2025 at 9:14 AM Richard Biener
wrote:
> On Mon, Jun 16, 2025 at 7:06 PM Segher Boessenkool
> wrote:
> >
> > Hi!
> >
> > On Mon, Jun 16, 2025 at 11:41:37AM +0200, Mark Wielaard wrote:
> > > > WaA is decided by the sourceware maintainers. The request form says
> > > > "email addre
On Mon, Jun 16, 2025 at 7:06 PM Segher Boessenkool
wrote:
>
> Hi!
>
> On Mon, Jun 16, 2025 at 11:41:37AM +0200, Mark Wielaard wrote:
> > > WaA is decided by the sourceware maintainers. The request form says
> > > "email address of person who approved request", but that is not who has
> > > the fi
Hi!
On Mon, Jun 16, 2025 at 11:41:37AM +0200, Mark Wielaard wrote:
> > WaA is decided by the sourceware maintainers. The request form says
> > "email address of person who approved request", but that is not who has
> > the final call :-) Which of course makes sense, the sourceware
> > maintainer
Hi Segher,
On Sun, Jun 15, 2025 at 11:07:15AM -0500, Segher Boessenkool wrote:
> On Sun, Jun 15, 2025 at 05:52:50PM +0200, Mark Wielaard wrote:
> > On Wed, Jun 11, 2025 at 10:40:02AM -0500, Segher Boessenkool wrote:
> > > On Wed, Jun 04, 2025 at 05:53:18PM -0600, Jeff Law via Gcc wrote:
> > > > If
Hi!
On Sun, Jun 15, 2025 at 05:52:50PM +0200, Mark Wielaard wrote:
> On Wed, Jun 11, 2025 at 10:40:02AM -0500, Segher Boessenkool wrote:
> > On Wed, Jun 04, 2025 at 05:53:18PM -0600, Jeff Law via Gcc wrote:
> > > On 6/3/25 1:41 PM, David Edelsohn via Gcc wrote:
> > > >What is not working with the
Hi Segher,
On Wed, Jun 11, 2025 at 10:40:02AM -0500, Segher Boessenkool wrote:
> On Wed, Jun 04, 2025 at 05:53:18PM -0600, Jeff Law via Gcc wrote:
> > On 6/3/25 1:41 PM, David Edelsohn via Gcc wrote:
> > >What is not working with the current system? What is this fixing?
> > It relies on the someo
On Wed, Jun 11, 2025 at 11:46 AM Segher Boessenkool <
seg...@kernel.crashing.org> wrote:
> On Wed, Jun 04, 2025 at 05:53:18PM -0600, Jeff Law via Gcc wrote:
> > On 6/3/25 1:41 PM, David Edelsohn via Gcc wrote:
> > >What is not working with the current system? What is this fixing?
> > It relies on
On Wed, Jun 04, 2025 at 05:53:18PM -0600, Jeff Law via Gcc wrote:
> On 6/3/25 1:41 PM, David Edelsohn via Gcc wrote:
> >What is not working with the current system? What is this fixing?
> It relies on the someone to shepherd the process and it's something that
> often gets pushed down on my daily
On 6/3/25 1:41 PM, David Edelsohn via Gcc wrote:
What is not working with the current system? What is this fixing?
It relies on the someone to shepherd the process and it's something that
often gets pushed down on my daily todo list. As a result nominations
don't happen or are extremely
On 6/3/25 4:16 AM, Richard Sandiford via Gcc wrote:
Hi,
At the moment, all reviewers and maintainers have to be appointed by the
Steering Committee. I wonder if we could add a second, more community-based
route: someone can be appointed as a reviewer or maintainer with the agreement
of a giv
Hi,
On Tue, Jun 03, 2025 at 11:47:41AM +0100, Jonathan Wakely via Gcc wrote:
> On Tue, 3 Jun 2025 at 11:21, Richard Sandiford via Gcc
> wrote:
> > At the moment, all reviewers and maintainers have to be appointed by the
> > Steering Committee. I wonder if we could add a second, more community-b
On 04/06/2025 14:57, David Edelsohn wrote:
On Wed, Jun 4, 2025 at 5:24 AM Richard Earnshaw (lists)
mailto:richard.earns...@arm.com>> wrote:
On 03/06/2025 20:41, David Edelsohn via Gcc wrote:
> On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford
mailto:richard.sandif...@arm.com>>
On Wed, Jun 4, 2025 at 5:24 AM Richard Earnshaw (lists) <
richard.earns...@arm.com> wrote:
> On 03/06/2025 20:41, David Edelsohn via Gcc wrote:
> > On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford <
> richard.sandif...@arm.com>
> > wrote:
> >
> >> David Edelsohn writes:
> >>> On Tue, Jun 3, 2025
On 03/06/2025 20:41, David Edelsohn via Gcc wrote:
> On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford
> wrote:
>
>> David Edelsohn writes:
>>> On Tue, Jun 3, 2025 at 6:22 AM Richard Sandiford via Gcc <
>> gcc@gcc.gnu.org>
>>> wrote:
>>>
Hi,
At the moment, all reviewers and maintai
On Tue, Jun 3, 2025 at 10:46 PM Richard Sandiford via Gcc
wrote:
>
> David Edelsohn via Gcc writes:
> > On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford
> > wrote:
> >
> >> David Edelsohn writes:
> >> > On Tue, Jun 3, 2025 at 6:22 AM Richard Sandiford via Gcc <
> >> gcc@gcc.gnu.org>
> >> > wrot
David Edelsohn via Gcc writes:
> On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford
> wrote:
>
>> David Edelsohn writes:
>> > On Tue, Jun 3, 2025 at 6:22 AM Richard Sandiford via Gcc <
>> gcc@gcc.gnu.org>
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> At the moment, all reviewers and maintainers have to b
On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford
wrote:
> David Edelsohn writes:
> > On Tue, Jun 3, 2025 at 6:22 AM Richard Sandiford via Gcc <
> gcc@gcc.gnu.org>
> > wrote:
> >
> >> Hi,
> >>
> >> At the moment, all reviewers and maintainers have to be appointed by the
> >> Steering Committee.
David Edelsohn writes:
> On Tue, Jun 3, 2025 at 6:22 AM Richard Sandiford via Gcc
> wrote:
>
>> Hi,
>>
>> At the moment, all reviewers and maintainers have to be appointed by the
>> Steering Committee. I wonder if we could add a second, more
>> community-based
>> route: someone can be appointed
On Tue, Jun 3, 2025 at 6:22 AM Richard Sandiford via Gcc
wrote:
> Hi,
>
> At the moment, all reviewers and maintainers have to be appointed by the
> Steering Committee. I wonder if we could add a second, more
> community-based
> route: someone can be appointed as a reviewer or maintainer with th
> Am 03.06.2025 um 12:22 schrieb Richard Sandiford via Gcc :
>
> Hi,
>
> At the moment, all reviewers and maintainers have to be appointed by the
> Steering Committee. I wonder if we could add a second, more community-based
> route: someone can be appointed as a reviewer or maintainer with t
On Tue, 3 Jun 2025 at 11:21, Richard Sandiford via Gcc wrote:
>
> Hi,
>
> At the moment, all reviewers and maintainers have to be appointed by the
> Steering Committee. I wonder if we could add a second, more community-based
> route: someone can be appointed as a reviewer or maintainer with the a
21 matches
Mail list logo