From: Wojciech Meyer <wojciech.meyer@googlemail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Andreas Rottmann <a.rottmann@gmx.at>, emacs-devel@gnu.org
Subject: Re: where to send patches
Date: Sun, 20 Mar 2011 23:06:40 +0000 [thread overview]
Message-ID: <87oc55s873.fsf@gmail.com> (raw)
In-Reply-To: <jwvvczrg1b2.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 09 Mar 2011 21:26:27 -0500")
Hi Stefan,
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Agreed. It occurred to me that we could even tweak M-x report-emacs-bug
>>> so that it notices when the report includes something that looks like
>>> a patch, and adds the corresponding debbugs tag.
>> People like to use this damn [PATCH] convention, so some time ago I
>> tweaked debbugs.gnu.org to recognize that in the same way as "Tags:
>> patch".
>
> That's good, but I think we should try and recognize the patch itself as
> well, since many people don't put any [PATCH] in the subject either.
Another point is that some VCS allow to format the patch automatically
along with an e-mail and put [PATCH] in the e-mail's subject header. I
would say that git-send-mail and git-format-patch do this. I am not sure
if bzr does it. Many people use format-patch and just paste it to the
e-mail subject. The chapter in the manual describes the process well
however it's not saying anything about the subject of the e-mail.
Thanks,
Wojciech
prev parent reply other threads:[~2011-03-20 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 17:32 [PATCH] Allow passing frame parameters to emacsclient Andreas Rottmann
2011-03-07 21:44 ` where to send patches [was Re: [PATCH] Allow passing frame parameters to emacsclient] Glenn Morris
2011-03-07 22:29 ` Andreas Rottmann
2011-03-08 2:05 ` Stefan Monnier
2011-03-09 19:50 ` where to send patches Glenn Morris
2011-03-09 20:24 ` Chong Yidong
2011-03-09 20:31 ` Glenn Morris
2011-03-10 2:26 ` Stefan Monnier
2011-03-20 23:06 ` Wojciech Meyer [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=87oc55s873.fsf@gmail.com \
--to=wojciech.meyer@googlemail.com \
--cc=a.rottmann@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).