public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Rick Macdonald <rickm@vsl.com>
To: Paul Traina <pst@juniper.net>
Cc: Bob Manson <bmanson@juniper.net>,
	gnats-devel@sourceware.cygnus.com, bug-gnats@gnu.org
Subject: Re: proclamation of intent
Date: Mon, 23 Aug 1999 11:13:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.10.9908231158010.20253-100000@sys4> (raw)
In-Reply-To: <19990823104833.A6147@red.juniper.net>

On Mon, 23 Aug 1999, Paul Traina wrote:

> How about if you drop a branch tag for gnats 3.x in now (in case folks want
> to do later 3.x releases, and commit a snapshot into the head as 4.0-alpha).
> This will give Rick and Ken a chance to change their front-ends to work with
> 4.0's commands, and we'll just screw the old network protocol.

I guess I'll buy that. Just make it the best you can, and we front-end
writers will go with it.

A few minor comments. I think you already have this issues "done right":

The fields and enums should have human-readable Help strings (multi-line
allowed?), and these strings need to be available to the client.

I would like that all configuration stuff is read and parsed by GNATS, and
when sent to the client, it is formatted and written by GNATS (gnatsd)
such that the client just parses it and doesn't have to check for errors
for remove comments. By this I mean that GNATS shouldn't just copy a gnats
admin file to the output (gnats used to do this; I removed a few cases of
it). This also makes the formatting of the info more consistent for
parsing by clients.

I think you should send out your proposed format of configuration info
that will be sent to clients that ask for it. I think TkGnats (me) and
gnatsweb (Ken and Matt) are the only people using this feature. I'd hate
for you to code a bunch of stuff only to have us bug you to change it
afterwards! Tcl and perl are great at parsing, but we might as well make
it simple for ourselves...

...RickM...

  parent reply	other threads:[~1999-08-23 11:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-18 11:21 Bob Manson
1999-08-18 12:36 ` Rick Macdonald
1999-08-18 13:13   ` Bob Manson
1999-08-18 13:37     ` Stephen Dahmen
1999-08-18 14:15     ` Rick Macdonald
1999-08-23 10:21     ` Rick Macdonald
1999-08-23 10:27       ` Paul Traina
1999-08-23 10:28         ` Rick Macdonald
1999-08-24  5:23         ` Mike Sutton
1999-08-24  9:56           ` Michael Richardson
1999-08-23 10:38       ` Bob Manson
1999-08-23 10:48         ` Paul Traina
1999-08-23 10:52           ` Bob Manson
1999-08-23 10:54             ` Paul Traina
1999-08-23 11:13           ` Rick Macdonald [this message]
1999-08-23 11:32             ` Tony Parent
1999-08-23 11:41               ` Rick Macdonald
1999-08-23 12:12             ` Bob Manson
1999-08-23 15:54               ` client info format ideas Rick Macdonald
1999-08-24  5:35             ` proclamation of intent Mike Sutton
1999-08-23 10:58         ` gnatsd accepting new PRs Rick Macdonald
1999-08-23 11:03           ` Bob Manson
1999-08-23 11:28             ` Tony Parent
     [not found] <Pine.LNX.4.04.9908241439580.17979-100000@intern.snow.nl>
1999-08-24  7:30 ` proclamation of intent Rick Macdonald

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=Pine.GSO.4.10.9908231158010.20253-100000@sys4 \
    --to=rickm@vsl.com \
    --cc=bmanson@juniper.net \
    --cc=bug-gnats@gnu.org \
    --cc=gnats-devel@sourceware.cygnus.com \
    --cc=pst@juniper.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).