[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#18428: Bug#760861: bug#18428: coreutils binary breaks coreutils docu

From: Pádraig Brady
Subject: bug#18428: Bug#760861: bug#18428: coreutils binary breaks coreutils documentation
Date: Tue, 09 Sep 2014 10:50:14 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2

On 09/09/2014 04:55 AM, Paul Eggert wrote:
> Subject: [PATCH 1/4] doc: mention which commands are optional

I was thinking that the bst way to do that would be to adjust things
so that the node wasn't installed if the command wasn't.  But it's better
to have this info generally available online also, so +1

> Subject: [PATCH 2/4] doc: rename "coreutils invocation" to "Multi-call

I had done essentially this in my local patch :) so +1

One caveat is that `coreutils --help` is now not accurate
in its presented texinfo node name.  Though I wouldn't
worry about that TBH, especially if relegating coreutils(1)
to a helper command in libexec.  Now some systems may very well like the
explicit option of `coreutils $cmd ...`, but since we need the
--coreutils-prog option too I'd be on for keeping this as a helper command.

I've attached the now optional patch to adjust node names,
which I'm 60:40 for applying since it works with pinfo.

> Subject: [PATCH 3/4] maint: prefer 'return status;' to 'exit (status);' in 
> 'main'

simpler so +1
There were a couple of syntax-check errors with this,
fixed in the attached.

> Subject: [PATCH 4/4] maint: avoid file-scope names of the form _[a-z]*


Marking this bug as done...


Attachment: multicall-info.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]