From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: patches: emacs-devel@ vs. debbugs.gnu.org
Date: Fri, 30 Jan 2015 20:45:58 +0000 [thread overview]
Message-ID: <87egqchu9l.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <dmLttHDTteLH5mU3AG1GVMEf195O5ZwUI2R4LzbDyi5@local> (Kelly Dean's message of "Wed, 28 Jan 2015 10:25:35 +0000")
>>>>> Kelly Dean <kelly@prtime.org> writes:
>>>>> Stefan Monnier wrote:
>>> I've been using this patch since the time I wrote it, and find it
>>> handy. I rarely use «C-h v» or «C-h f» anymore.
>> Looks good to me,
> What do I need to do with this patch? Send it to bug-gnu-emacs for a
> ticket number?
IMO, it never harms to have a bug# assigned to the case, as it
allows for everything related to be linked to a single URI.
As to /how/ to file bug reports, – my own preference is to send
them to submit@ (/not/ bug-gnu-emacs@), as it allows me to
specify Severity: and possibly Version: and Tags:. Like:
Subject: hello.el: says goodbye
To: submit at debbugs dot gnu dot org
Package: emacs
Version: 24.4
Severity: minor
Tags: patch
[The report comes here. The patch is in a separate MIME part.]
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
prev parent reply other threads:[~2015-01-30 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 23:06 [Old patch] Unify fn and var help to make learning elisp a little easier Kelly Dean
2015-01-20 23:17 ` Alexis
2015-01-21 14:37 ` Stefan Monnier
2015-01-28 10:25 ` Kelly Dean
2015-01-28 11:27 ` Artur Malabarba
2015-02-04 6:42 ` Kelly Dean
2015-02-04 12:05 ` Artur Malabarba
2015-02-05 3:59 ` Kelly Dean
2015-02-05 17:33 ` Artur Malabarba
2015-02-05 17:51 ` Dmitry Gutov
2015-02-06 5:23 ` Kelly Dean
2015-02-06 6:01 ` Dmitry Gutov
2015-02-06 8:47 ` Artur Malabarba
2015-02-06 14:46 ` Stefan Monnier
2015-01-30 20:05 ` Artur Malabarba
2015-01-30 20:14 ` Artur Malabarba
2015-01-30 20:45 ` Ivan Shmakov [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=87egqchu9l.fsf_-_@violet.siamics.net \
--to=ivan@siamics.net \
--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 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).