From: Steinar Bang <sb@dod.no>
Subject: Re: How about a Gnus Bugzilla?
Date: Fri, 15 Oct 2004 07:27:23 +0200 [thread overview]
Message-ID: <873c0g5z5w.fsf@dod.no> (raw)
In-Reply-To: <m3655dotpw.fsf@defun.localdomain>
>>>>> Jesper Harder <harder@ifa.au.dk>:
> Is there a good Emacs interface to bugzilla? If not, I won't be using
> it -- bugzilla from a web browser is a PITA.
> I've stopped contributing bug reports to projects that use bugzilla
> or (even worse) sourceforge because the web based interface is just
> too damn annoying and primitive.
IMO, bugzilla isn't too bad as web UIs go. I have _seen_ bad, and
bugzilla doesn't even come close. But I see your point.
> The general idea of handling bug reports in a more structured way
> might be nice, though.
That's what triggered it for me.
I usually post enhancement requests here, and outright, reproducable,
bugs on gnus-bug. When I'm not sure if it's a bug or not, I keep a
little conversation with myself here, and hope that a developer picks
it up, if it actually turns up or not.
But there's a feeling that things are lost in the noise from general
discussion. There are things that have been debated earlier that
keeps popping up again.
prev parent reply other threads:[~2004-10-15 5:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 11:04 Steinar Bang
2004-10-14 17:51 ` Xavier Maillard
2004-10-14 18:44 ` Ted Zlatanov
2004-10-14 19:17 ` Steinar Bang
2004-10-15 15:08 ` Ted Zlatanov
2004-10-15 19:28 ` Steinar Bang
2004-10-19 13:41 ` Bjørn Mork
2004-10-14 20:14 ` Reiner Steib
2004-10-14 21:31 ` Xavier Maillard
2004-10-15 8:40 ` Adam Sjøgren
2004-10-16 9:03 ` Xavier Maillard
2004-10-14 19:12 ` Steinar Bang
2004-10-14 20:22 ` Wes Hardaker
2004-10-15 5:16 ` Steinar Bang
2004-10-14 21:50 ` Jesper Harder
2004-10-15 5:27 ` Steinar Bang [this message]
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=873c0g5z5w.fsf@dod.no \
--to=sb@dod.no \
/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 NNTP newsgroup(s).