On Fri, 27 Jul 2018, Alexander von Gluck IV wrote:
> >> It's much better for issues to be identified within a day or two of the
> >> commit causing them than many months later, possibly only after a release
> >> has come out with the issue - but that requires an ongoing commitment to
> >> keep
On Fri, 27 Jul 2018, Ramana Radhakrishnan wrote:
> Joseph,
>
> A lot of such information seems to come out from a number of reviewers
> only during patch review from new contributors. Would you mind
> improving https://gcc.gnu.org/contribute.html and especially around
> "Testing patches" or
July 27, 2018 6:59 AM, "Ramana Radhakrishnan" wrote:
> On Thu, Jul 26, 2018 at 6:26 PM, Joseph Myers wrote:
>
>> On Mon, 16 Jul 2018, Alexander von Gluck IV wrote:
>>
>>> * We have been dragging these around since gcc 4.x.
>>> * Some tweaks will likely be needed, but this gets our foot
>>> in
On Thu, Jul 26, 2018 at 6:26 PM, Joseph Myers wrote:
> On Mon, 16 Jul 2018, Alexander von Gluck IV wrote:
>
>> * We have been dragging these around since gcc 4.x.
>> * Some tweaks will likely be needed, but this gets our foot
>> in the door.
>>
>> Authors:
>> Fredrik Holmqvist
>> Jerome
On Mon, 16 Jul 2018, Alexander von Gluck IV wrote:
> * We have been dragging these around since gcc 4.x.
> * Some tweaks will likely be needed, but this gets our foot
> in the door.
>
> Authors:
> Fredrik Holmqvist
> Jerome Duval
> Augustin Cavalier
> François Revol
> Simon South
>
* We have been dragging these around since gcc 4.x.
* Some tweaks will likely be needed, but this gets our foot
in the door.
Authors:
Fredrik Holmqvist
Jerome Duval
Augustin Cavalier
François Revol
Simon South
Jessica Hamilton
Ithamar R. Adema
Oliver Tappe
Jonathan Schleifer
