(Apologies if you get this twice, the mailing list didn't like the html
attachment in the first attempt).
We frequently get malformatted patches, and it's been brought to my
attention that some people don't even make the effort to read the GNU
coding standards before trying to contribute code.
> On Apr 22, 2016, at 12:21 PM, Bernd Schmidt wrote:
>
> (Apologies if you get this twice, the mailing list didn't like the html
> attachment in the first attempt).
>
> We frequently get malformatted patches, and it's been brought to my attention
> that some people don't even make the effort
On 04/22/2016 12:42 PM, paul_kon...@dell.com wrote:
On Apr 22, 2016, at 12:21 PM, Bernd Schmidt wrote:
(Apologies if you get this twice, the mailing list didn't like the html
attachment in the first attempt).
We frequently get malformatted patches, and it's been brought to my attention
tha
On 04/22/2016 07:21 PM, Bernd Schmidt wrote:
> (Apologies if you get this twice, the mailing list didn't like the html
> attachment in the first attempt).
>
> We frequently get malformatted patches, and it's been brought to my attention
> that some people don't even make the effort to read the GNU
On 04/22/2016 10:42 AM, paul_kon...@dell.com wrote:
On Apr 22, 2016, at 12:21 PM, Bernd Schmidt
wrote:
(Apologies if you get this twice, the mailing list didn't like the
html attachment in the first attempt).
We frequently get malformatted patches, and it's been brought to my
attention that
On 04/22/2016 09:45 PM, Sandra Loosemore wrote:
On 04/22/2016 10:42 AM, paul_kon...@dell.com wrote:
Would you expect people to conform to the abridged version or the
full standard? If the full standard, then publishing an abridged
version is not a good idea, it will just cause confusion. Let
Bernd Schmidt writes:
> (Apologies if you get this twice, the mailing list didn't like the html
> attachment in the first attempt).
>
> We frequently get malformatted patches, and it's been brought to my
> attention that some people don't even make the effort to read the GNU
> coding standards
On 04/22/2016 12:21 PM, Bernd Schmidt wrote:
> (Apologies if you get this twice, the mailing list didn't like the
> html attachment in the first attempt).
>
> We frequently get malformatted patches, and it's been brought to my
> attention that some people don't even make the effort to read the GNU
On 05/02/2016 02:40 PM, Carlos O'Donell wrote:
However, in the end, I think that yet-another-document is not the
solution we want. What we actually need is a program that just formats
your source according to the GNU Coding Style and that way you can always
tell your users "Run indent" and be do
Jeff Law writes:
> On 05/02/2016 02:40 PM, Carlos O'Donell wrote:
>>
>> However, in the end, I think that yet-another-document is not the
>> solution we want. What we actually need is a program that just formats
>> your source according to the GNU Coding Style and that way you can always
>> tell y
On 05/03/2016 03:59 PM, Richard Sandiford wrote:
> Jeff Law writes:
>> On 05/02/2016 02:40 PM, Carlos O'Donell wrote:
>>>
>>> However, in the end, I think that yet-another-document is not the
>>> solution we want. What we actually need is a program that just formats
>>> your source according to th
On Tue, 3 May 2016, Richard Sandiford wrote:
> And sometimes there are multiple acceptable ways of writing the same code.
> Which wins is an aesthetic choice, which tools tend to be bad at handling.
> E.g. if a parameter list is too long for a line, there's often a choice
> of how to balance the p
On 05/03/2016 09:59 PM, Richard Sandiford wrote:
And sometimes there are multiple acceptable ways of writing the same code.
Which wins is an aesthetic choice, which tools tend to be bad at handling.
E.g. if a parameter list is too long for a line, there's often a choice
of how to balance the par
On 05/03/2016 06:39 PM, Bernd Schmidt wrote:
> On 05/03/2016 09:59 PM, Richard Sandiford wrote:
>>
>> And sometimes there are multiple acceptable ways of writing the
>> same code. Which wins is an aesthetic choice, which tools tend to
>> be bad at handling. E.g. if a parameter list is too long for
14 matches
Mail list logo
