From: Rick Macdonald <rickm@vsl.com>
To: Tony Parent <tony.parent@lsil.com>
Cc: Paul Traina <pst@juniper.net>, 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:41:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.9908231236450.20253-100000@sys4> (raw)
In-Reply-To: <14273.37541.349921.468037@merlin.co.lsil.com>
On Mon, 23 Aug 1999, Tony Parent wrote:
> I also use it in my Java front end, and Java isn't as good at parsing as
> perl/tcl, so I would add my vote to making it (parsing) as easy and
> consistent as possible.
Tony - I warned/suggested last week that we _may_ find that we need the
same info dumped out in different formats for Tcl, perl, [c]sh, etc. It's
not clear yet whether or not this is reequired but Bob wasn't against the
idea.
...RickM...
next prev parent reply other threads:[~1999-08-23 11:41 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
1999-08-23 11:32 ` Tony Parent
1999-08-23 11:41 ` Rick Macdonald [this message]
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.9908231236450.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 \
--cc=tony.parent@lsil.com \
/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).