>> Hi Jose,
>>
>> On Sat, Mar 08, 2025 at 02:17:52PM +0100, Jose E. Marchesi wrote:
>>> > Since you already have a fork on the (experimental) forge we could
>>> > also move your fork under https://forge.sourceware.org/gcc that way
>>> > you can experiment with merge requests if you like. Even if
> Hi Jose,
>
> On Sat, Mar 08, 2025 at 02:17:52PM +0100, Jose E. Marchesi wrote:
>> > Since you already have a fork on the (experimental) forge we could
>> > also move your fork under https://forge.sourceware.org/gcc that way
>> > you can experiment with merge requests if you like. Even if all yo
Hi Jose,
On Sat, Mar 08, 2025 at 02:17:52PM +0100, Jose E. Marchesi wrote:
> > Since you already have a fork on the (experimental) forge we could
> > also move your fork under https://forge.sourceware.org/gcc that way
> > you can experiment with merge requests if you like. Even if all your
> > pat
> Hi,
>
> On Fri, Mar 07, 2025 at 03:57:40PM +, Richard Earnshaw (lists) via Gcc
> wrote:
>> On 07/03/2025 15:41, Jose E. Marchesi via Gcc wrote:
>> > The Steering Committee has decided not to merge the Algol 68 Front-End
>> > in master at this point, but is ok with us using a branch in gcc.
Hi,
On Fri, Mar 07, 2025 at 03:57:40PM +, Richard Earnshaw (lists) via Gcc
wrote:
> On 07/03/2025 15:41, Jose E. Marchesi via Gcc wrote:
> > The Steering Committee has decided not to merge the Algol 68 Front-End
> > in master at this point, but is ok with us using a branch in gcc.git to
> > d
On 07/03/2025 15:41, Jose E. Marchesi via Gcc wrote:
>
> Hello people!
>
> The Steering Committee has decided not to merge the Algol 68 Front-End
> in master at this point, but is ok with us using a branch in gcc.git to
> develop and maintain the front-end as well as a mailing list in
> algo...@g
