On Wed, 9 Jan 2019, Paul Koning wrote:
> Is there, or should there be, a distinction between primary and
> non-primary platforms? While platform bugs typically require fixes in
> platform-specific code, I would think we would want to stay away from
> bugfixes in minor platforms during stage
On Wed, 9 Jan 2019, Paul Koning wrote:
> Is there, or should there be, a distinction between primary and
> non-primary platforms? While platform bugs typically require fixes in
> platform-specific code, I would think we would want to stay away from
> bugfixes in minor platforms during stage
On 1/9/19 4:02 AM, Jonathan Wakely wrote:
+extra care on not introducing new regressions - fixing bugs at all cost
ISTM that this should be either "at any cost" or "at all costs". The
current wording can't make up its mind if it's singular or plural.
Agreed, as a native english speaker, 'at
On Wed, 9 Jan 2019, Paul Koning wrote:
>
>
> > On Jan 9, 2019, at 3:42 AM, Tom de Vries wrote:
> >
> > [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
> >
> > The current formulation for the description of Stage 4 here (
> > https://gcc.gnu.org/develop.html ) is:
> >
On Wed, 9 Jan 2019, Paul Koning wrote:
>
>
> > On Jan 9, 2019, at 3:42 AM, Tom de Vries wrote:
> >
> > [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
> >
> > The current formulation for the description of Stage 4 here (
> > https://gcc.gnu.org/develop.html ) is:
> >
> On Jan 9, 2019, at 3:42 AM, Tom de Vries wrote:
>
> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
>
> The current formulation for the description of Stage 4 here (
> https://gcc.gnu.org/develop.html ) is:
> ...
> During this period, the only (non-documentation)
> On Jan 9, 2019, at 3:42 AM, Tom de Vries wrote:
>
> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
>
> The current formulation for the description of Stage 4 here (
> https://gcc.gnu.org/develop.html ) is:
> ...
> During this period, the only (non-documentation)
On Wed, 9 Jan 2019 at 08:41, Tom de Vries wrote:
>
> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
>
> The current formulation for the description of Stage 4 here (
> https://gcc.gnu.org/develop.html ) is:
> ...
> During this period, the only (non-documentation) changes
On Wed, 9 Jan 2019 at 08:41, Tom de Vries wrote:
>
> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
>
> The current formulation for the description of Stage 4 here (
> https://gcc.gnu.org/develop.html ) is:
> ...
> During this period, the only (non-documentation) changes
On Wed, 9 Jan 2019, Tom de Vries wrote:
> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
>
> The current formulation for the description of Stage 4 here (
> https://gcc.gnu.org/develop.html ) is:
> ...
> During this period, the only (non-documentation) changes that may
On Wed, 9 Jan 2019, Tom de Vries wrote:
> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
>
> The current formulation for the description of Stage 4 here (
> https://gcc.gnu.org/develop.html ) is:
> ...
> During this period, the only (non-documentation) changes that may
[ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
The current formulation for the description of Stage 4 here (
https://gcc.gnu.org/develop.html ) is:
...
During this period, the only (non-documentation) changes that may be
made are changes that fix regressions.
Other
[ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
The current formulation for the description of Stage 4 here (
https://gcc.gnu.org/develop.html ) is:
...
During this period, the only (non-documentation) changes that may be
made are changes that fix regressions.
Other
13 matches
Mail list logo
