public inbox for
help / color / mirror / Atom feed
From: Yngve Svendsen <>
Subject: Re: gnats/264: gnatsd help text should match man page and manual
Date: Mon, 17 Sep 2001 06:44:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR gnats/264; it has been noted by GNATS.

From: Yngve Svendsen <>
To:,Milan Zamazal <>
Subject: Re: gnats/264: gnatsd help text should match man page and
Date: Mon, 17 Sep 2001 15:37:14 +0200

 The following patch adds APPN, REPL and DBDESC lines to the gnatsd help text.
 - Yngve
 Index: cmds.c
 RCS file: /cvs/gnats/gnats/gnats/cmds.c,v
 retrieving revision 1.58
 diff -u -p -r1.58 cmds.c
 --- cmds.c	2001/09/06 18:59:57	1.58
 +++ cmds.c	2001/09/17 13:38:21
 @@ -1722,6 +1722,10 @@ GNATS_help (int ac ATTRIBUTE_UNUSED, cha
     printf ("%d-   EDIT <PR>               check in edited <PR>\r\n",
 +  printf ("%d-   APPN <PR> <field>       append to contents of <field> in 
 +  printf ("%d-   REPL <PR> <field>       replace contents of <field> in 
     printf ("%d-   SUBM                    submit a new PR\r\n",
     printf ("%d-   CHDB <database> [<user> <passwd>]\r\n",
 @@ -1733,6 +1737,8 @@ GNATS_help (int ac ATTRIBUTE_UNUSED, cha
     printf ("%d-   USER                    Report current access level\r\n",
     printf ("%d-   DBLS                    list databases known to server\r\n",
 +  printf ("%d-   DBDESC <database>       return description of 
     printf ("%d-   EXPR <expression>       restrict search to PRs that 
 match the\r\n",

             reply	other threads:[~2001-09-17  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17  6:44 Yngve Svendsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-17  6:42 yngves
2001-09-17  6:24 yngve.svendsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).