unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: The bug tracker...again
Date: Tue, 23 Aug 2011 14:54:47 -0400	[thread overview]
Message-ID: <877h64yn48.fsf@red-bean.com> (raw)
In-Reply-To: <E1QvuKW-0007fY-2G@fencepost.gnu.org> (Richard Stallman's message of "Tue, 23 Aug 2011 13:00:00 -0400")

Richard Stallman <rms@gnu.org> writes:
>    I'm not sure if Richard meant email per se, or merely that bug-reporting
>    must be possible from within Emacs, i.e., without switching to a
>    separate web-browsing program.
>
>I meant email, strictly and literally.
>
>    If that's the *real* requirement, then any bug tracker with a decent
>    network API would probably work, because we could teach Emacs to speak
>    that API for reporting new bugs.
>
>It is fine if such an interface exists, but it does not substitute
>for access by email.

Thanks.  I realized later you did mean it literally.  (Stephen Turnbull
pointed out to me that email's well-debugged offline queueing mechanism
is the important thing here, not its user interface.)

Many bug trackers have this, nowadays, anyway.  Redmine is one such:

  https://we.riseup.net/cgdev/using-email-with-redmine

Obviously, if a bug tracker supports email intake and outflow, then
that's an API of sorts, so Emacs can provide a non-email form-based way
for users to report bugs, and if absolutely necessary convert that to an
email.  But it's better to use a real network API if available -- then
the user can get real-time confirmation of the bug identifier, etc.
This is something debbugs does not do, AFAIK.

-Karl



  reply	other threads:[~2011-08-23 18:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 23:43 Fixing C-x DEL bug Richard Stallman
2011-08-19  0:16 ` Wolfgang Jenkner
2011-08-19 23:12   ` Richard Stallman
2011-08-19 23:48     ` Glenn Morris
2011-08-20  8:18       ` Eli Zaretskii
2011-08-20 15:56       ` Richard Stallman
2011-08-20 16:22         ` Glenn Morris
2011-08-22 14:48           ` Richard Stallman
2011-08-22 19:15     ` The bug tracker...again (was: Fixing C-x DEL bug) Deniz Dogan
2011-08-22 20:03       ` The bug tracker...again Glenn Morris
2011-08-22 20:05       ` Karl Fogel
2011-08-23 17:00         ` Richard Stallman
2011-08-23 18:54           ` Karl Fogel [this message]
2011-08-24  2:06             ` Chong Yidong
2011-08-19  8:18 ` Fixing C-x DEL bug Alan Mackenzie
2011-08-19  8:32   ` Eli Zaretskii
2011-08-19  8:34     ` Alan Mackenzie
2011-08-20 15:56   ` Richard Stallman
2011-08-21  8:50     ` Alan Mackenzie
2011-08-21 22:14       ` Richard Stallman
2011-08-22 11:26         ` Alan Mackenzie
2011-09-22 18:19           ` Wolfgang Jenkner

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=877h64yn48.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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