On Wed, Feb 14, 2018 at 10:53:04PM +0100, Christophe de Dinechin wrote:
>
>
> > On 14 Feb 2018, at 14:37, Christophe Fergeau wrote:
> >
> > On Thu, Feb 08, 2018 at 12:25:30PM +0100, Christophe de Dinechin wrote:
> >> From: Christophe de Dinechin
> >>
> >> The objective of these guidelines is
> On 14 Feb 2018, at 14:37, Christophe Fergeau wrote:
>
> On Thu, Feb 08, 2018 at 12:25:30PM +0100, Christophe de Dinechin wrote:
>> From: Christophe de Dinechin
>>
>> The objective of these guidelines is that:
>> - We avoid introducing new warnings
>> - We know how to fix old ones
>> - We do
On Thu, Feb 08, 2018 at 12:25:30PM +0100, Christophe de Dinechin wrote:
> From: Christophe de Dinechin
>
> The objective of these guidelines is that:
> - We avoid introducing new warnings
> - We know how to fix old ones
> - We don't have to isolate whitespace changes when submitting patches,
>
From: Christophe de Dinechin
The objective of these guidelines is that:
- We avoid introducing new warnings
- We know how to fix old ones
- We don't have to isolate whitespace changes when submitting patches,
i.e. someone who use tools that automatically strip whitespaces and
therefore "repai
