From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: possible emacs bug, need help with repro
Date: Wed, 02 Feb 2011 09:44:19 -0500 [thread overview]
Message-ID: <jwvd3na1oq5.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.3.1296617044.28222.help-gnu-emacs@gnu.org
> filed bug http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7946 . This is the
> first Emacs bug I've filed in memory. Does anyone know what the timeline
> will be like? I'd like to give any additional details while I have it fresh
> in mind.
Very unpredictable. Depends on whether it piques the curiosity of
someone, and how busy are those someones.
Stefan
prev parent reply other threads:[~2011-02-02 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 15:59 possible emacs bug, need help with repro Le Wang
2011-01-30 20:33 ` Stephen Berman
2011-02-02 3:23 ` Le Wang
[not found] ` <mailman.3.1296617044.28222.help-gnu-emacs@gnu.org>
2011-02-02 14:44 ` Stefan Monnier [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
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=jwvd3na1oq5.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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.
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).