From: Jason Molenda <jason@molenda.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: a bit of gnatsweb info
Date: Wed, 17 Jan 2001 14:36:00 -0000 [thread overview]
Message-ID: <20010117143608.A27685@shell17.ba.best.com> (raw)
Message-ID: <20010117143600.-x-t-1e0BGsF8j4FAWa6bweoIWD1kNyu0WFEoypf1Bs@z> (raw)
In-Reply-To: <20010117173700.A9515@disaster.jaj.com>
> <voice style="johnny carson">
>
> I did not know that.
>
> </voice>
:-)
> The command-line utils don't seem to be able to provide the same details
> as any of the others (according to the GNATS docs),
You shouldn't be giving up anything by using the command line
interfaces. Most everyone at Cygnus used the command line or emacs
interfaces to gnats for years. You don't get pull-downs to click
on, but all the features/facilities are there if you use the right
command line options.
BTW I should note that the gnatsweb facility for uploading a file
into a PR is a gnatsweb-only mechanism. As far as I know, no other
front ends are able to decode these attachments. It's one of the
(numerous) weaknesses of gnats that it doesn't have a standardized
facility for attaching files to a PR.
(there's no technical reason why the other front ends couldn't decode
the gnatsweb attachments; it's just that no one has done it yet AFAIK)
Jason
next prev parent reply other threads:[~2001-01-17 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 Phil Edwards
2001-01-17 12:55 ` Phil Edwards
2001-12-31 19:40 ` Jason Molenda
2001-01-17 13:15 ` Jason Molenda
2001-12-31 19:40 ` Phil Edwards
2001-01-17 14:27 ` Phil Edwards
2001-12-31 19:40 ` Jason Molenda [this message]
2001-01-17 14:36 ` Jason Molenda
2001-12-31 19:40 ` Tom Tromey
2001-01-19 13:33 ` Tom Tromey
2001-12-31 19:40 ` Gerald Pfeifer
2001-01-17 13:57 ` Gerald Pfeifer
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=20010117143608.A27685@shell17.ba.best.com \
--to=jason@molenda.com \
--cc=overseers@sourceware.cygnus.com \
--cc=pedwards@disaster.jaj.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).