From: Harald Hanche-Olsen <hanche@math.ntnu.no>
To: emacs-devel@gnu.org
Subject: Re: please review bug #13141
Date: Mon, 21 Jan 2013 16:26:53 +0100 (CET) [thread overview]
Message-ID: <20130121.162653.2105027028246728109.hanche@math.ntnu.no> (raw)
In-Reply-To: <F4D2F729B52B4D48B2CFF5C47D00E4A0@us.oracle.com>
[Drew Adams <drew.adams@oracle.com> (2013-01-21 15:05:12 UTC)]
> That doesn't mean that the emacs session where you submit the report
> must be an emacs -Q session. And some bug reports do not require a
> recipe from emacs -Q, though that's always a good idea.
I don't know about others, but I can't possibly send email from an
emacs -Q session without going through a lot of trouble. Which means
recent input and messages are almost always irrelevant. It might make
sense to only include this data provided
(y-or-n-p "Did you encounter the bug just now in this emacs session?")
- Harald
next prev parent reply other threads:[~2013-01-21 15:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 7:18 please review bug #13141 Andrey Paramonov
2013-01-21 15:05 ` Drew Adams
2013-01-21 15:26 ` Harald Hanche-Olsen [this message]
2013-01-21 17:29 ` Eli Zaretskii
2013-01-21 22:20 ` Drew Adams
2013-01-22 4:15 ` Xue Fuqiao
2013-01-22 6:40 ` Drew Adams
2013-01-22 7:51 ` Xue Fuqiao
2013-01-22 15:10 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2013-01-19 23:10 Drew Adams
2013-01-19 23:20 ` Alan Mackenzie
2013-01-19 23:59 ` Drew Adams
2013-01-20 0:12 ` Xue Fuqiao
2013-01-20 7:16 ` Stephen J. Turnbull
2013-01-20 10:33 ` Xue Fuqiao
2013-01-20 17:08 ` Eli Zaretskii
2013-01-20 18:41 ` bug#13141: " Richard Stallman
2013-01-20 21:21 ` Drew Adams
2013-01-21 2:39 ` Stephen J. Turnbull
2013-01-20 10:50 ` Alan Mackenzie
2013-01-20 12:02 ` Xue Fuqiao
2013-01-20 20:27 ` Glenn Morris
2013-01-21 2:52 ` Stephen J. Turnbull
2013-01-20 17:40 ` Drew Adams
2013-01-21 4:24 ` Drew Adams
2013-01-19 23:21 ` Drew Adams
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=20130121.162653.2105027028246728109.hanche@math.ntnu.no \
--to=hanche@math.ntnu.no \
--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.