[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Should we split the project into two branches?
|
From: |
Richard Frith-Macdonald |
|
Subject: |
Re: Should we split the project into two branches? |
|
Date: |
Mon, 14 Feb 2022 13:23:11 +0000 |
> On 14 Feb 2022, at 11:43, Max Chan <xcvista@me.com> wrote:
>
> Dear List,
>
> There are over and over again arguments on moving on to LLVM/clang for latest
> language features versus maintaining compatibility with old/uncommon
> platforms and GCC,
Really this is simply not the case among GNUstep developers.
Those of us who actually use the stuff just work with whatever we prefer/need,
because GNUstep already works with both toolchains.
- Should we split the project into two branches?, Max Chan, 2022/02/14
- Re: Should we split the project into two branches?,
Richard Frith-Macdonald <=
- Re: Should we split the project into two branches?, Max Chan, 2022/02/14
- Re: Should we split the project into two branches?, Richard Frith-Macdonald, 2022/02/14
- Re: Should we split the project into two branches?, Andreas Fink, 2022/02/14
- Re: Should we split the project into two branches?, Frederik Seiffert, 2022/02/14
- Re: Should we split the project into two branches?, Frederik Seiffert, 2022/02/14
- Re: Should we split the project into two branches?, Riccardo Mottola, 2022/02/14
- Re: Should we split the project into two branches?, Max Chan, 2022/02/14
- Re: Should we split the project into two branches?, Riccardo Mottola, 2022/02/15
- Re: Should we split the project into two branches?, Max Chan, 2022/02/15
- Re: Should we split the project into two branches?, Andreas Fink, 2022/02/15