>> A single call of the fprintf() function is sufficient for the desired
>> display of the usage information.
>
> This seems like churn that doesn't actually fix anything.
Will it matter occasionally to reduce the number of function calls
by combining several text fragments into the passing of
On Thu, 24 Dec 2015 13:38:01 +0100
SF Markus Elfring wrote:
> A single call of the fprintf() function is sufficient for the desired
> display of the usage information.
This seems like churn that doesn't actually fix anything.
jon
--
To unsubscribe from this list: send the line "unsubscribe
From: Markus Elfring
Date: Thu, 24 Dec 2015 13:10:19 +0100
A single call of the fprintf() function is sufficient for the desired
display of the usage information.
Signed-off-by: Markus Elfring
---
Documentation/accounting/getdelays.c | 12 ++--
1 file changed, 6 insertions(+), 6
>> A single call of the fprintf() function is sufficient for the desired
>> display of the usage information.
>
> This seems like churn that doesn't actually fix anything.
Will it matter occasionally to reduce the number of function calls
by combining several text fragments into the passing of
From: Markus Elfring
Date: Thu, 24 Dec 2015 13:10:19 +0100
A single call of the fprintf() function is sufficient for the desired
display of the usage information.
Signed-off-by: Markus Elfring
---
On Thu, 24 Dec 2015 13:38:01 +0100
SF Markus Elfring wrote:
> A single call of the fprintf() function is sufficient for the desired
> display of the usage information.
This seems like churn that doesn't actually fix anything.
jon
--
To unsubscribe from this list:
6 matches
Mail list logo