Hello!
Thanks for taking care of the manual! Just a very very partial review…
"Brent W. Baccala" skribis:
> +@node rpctrace
> +@section rpctrace
The convention would be to call this section “Invoking rpctrace”, so:
@node Invoking rpctrace
@section Invoking @command{rpctrace}
> +@example
On Tue, Nov 1, 2016 at 5:15 AM, Samuel Thibault
wrote:
>
> GNU projects usually don't have man pages, but info pages. The
> doc/hurd.texi indeed doesn't have any part for rpctrace. It should :)
>
>
What an embarrassing *faux pas*! It's like fumbling to put the Metro card
in the turnstile, like
Hello,
Brent W. Baccala, on Mon 31 Oct 2016 21:00:53 -1000, wrote:
> How about writing a man page?
GNU projects usually don't have man pages, but info pages. The
doc/hurd.texi indeed doesn't have any part for rpctrace. It should :)
I also notice that "info settrans" doesn't seem to bring to th
Hmm... maybe somebody on the list will fix the gsync bug, since I don't
know how...
...what can I do in the meantime...
How about writing a man page?
agape
brent
rpctrace.1
Description: Binary data