Re: [PATCH v3 1/4] reggroups: Add test and docs for `info reg $reggroup` feature

[Simon Marchi <simon dot marchi at polymtl dot ca>]

On 2017-12-19 11:23, Eli Zaretskii wrote:
> > From: Stafford Horne <shorne@gmail.com>
> > Cc: Openrisc <openrisc@lists.librecores.org>,	Stafford Horne 
> > <shorne@gmail.com>
> > Date: Tue, 19 Dec 2017 23:22:54 +0900
> >
> > Until now this feature has existed but was not documented.  Adding 
> > docs
> > and tests.
>
> Thanks!
>
> > +@item info registers @var{reggroup} @dots{}
> > +Print the name and value of the registers in each of the specified
> > +@var{reggroup}.  The @var{reggoup} can be any of those returned by
>
> Please use "@var{reggroup}s", with the trailing "s", otherwise this is
> not correct English.
>
> > +@code{maint print reggroups}.
>
> Please add here a cross-reference to the node where "maint print
> reggroups" is described.

Is it ok for a non-maint command to refer to a maint command?  AFAIK, we 
don't expect an average user to have to use maintenance commands when 
using GDB.  So maybe "maint print reggroups" should be promoted to a 
non-maint command (e.g. info register-groups)?

Simon