all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: `report-emacs-bug' prompting rework
Date: Fri, 10 Feb 2012 14:25:37 -0500	[thread overview]
Message-ID: <87lioapk26.fsf@lifelogs.com> (raw)
In-Reply-To: 87vcney2in.fsf@gnus.org

On Fri, 10 Feb 2012 19:19:44 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> As previously discussed (like, a year ago), the prompting sequence when
LI> sending bug reports, especially from "emacs -Q", was kinda
LI> unsatisfactory.  (The main point was that it required that you had a
LI> valid-ish From header, even though you might end up sending the message
LI> through mailclient.el, which will then just rewrite your From header,
LI> anyway.)

LI> Fixing this required a bit of refactoring of the sendmail.el/Message
LI> setup functions, but hopefully I didn't screw up anything too badly.

LI> And the prompting sequence looks OK to me now, but please let me know if
LI> anything is wonky.

I still think Emacs bugs should be simply reported through a HTTP (REST
or whatever) call.  That would cover the most users and we can use
confirmation e-mails to avoid spamming.

Ted




  reply	other threads:[~2012-02-10 19:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 18:19 `report-emacs-bug' prompting rework Lars Ingebrigtsen
2012-02-10 19:25 ` Ted Zlatanov [this message]
2012-02-11  2:26   ` Jason Rumney
2012-02-11  4:37     ` Stephen J. Turnbull
2012-02-11 14:31     ` Ted Zlatanov
2012-02-13 21:54       ` Ted Zlatanov
2012-02-13 21:57         ` Lars Ingebrigtsen
2012-02-14  0:01           ` Ted Zlatanov
2012-02-14  6:52             ` Chong Yidong
2012-02-19 13:05             ` Dimitri Fontaine
2012-02-21 21:52               ` Ted Zlatanov
2012-02-10 19:26 ` bug#9074: " Glenn Morris

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=87lioapk26.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.