Re: Documentation-getdelays: Less function calls in usage()

2015-12-24 Thread SF Markus Elfring
>> 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

Re: [PATCH 3/3] Documentation-getdelays: Less function calls in usage()

2015-12-24 Thread Jonathan Corbet
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

[PATCH 3/3] Documentation-getdelays: Less function calls in usage()

2015-12-24 Thread SF Markus Elfring
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

Re: Documentation-getdelays: Less function calls in usage()

2015-12-24 Thread SF Markus Elfring
>> 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

[PATCH 3/3] Documentation-getdelays: Less function calls in usage()

2015-12-24 Thread SF Markus Elfring
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 ---

Re: [PATCH 3/3] Documentation-getdelays: Less function calls in usage()

2015-12-24 Thread Jonathan Corbet
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: