unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michal Nazarewicz <mpn@google.com>, emacs-devel@gnu.org
Subject: Re: Sending multiple patches
Date: Mon, 02 Jun 2014 11:47:51 -0400	[thread overview]
Message-ID: <ygbnubgvo8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwv4n038o3p.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 02 Jun 2014 09:17:37 -0400")

Stefan Monnier wrote:

>> Will a threaded messages to bug-gnu-emacs@gnu.org do?
>
> I think currently this would generate N distinct bug numbers

Yes, it probably would. See http://debbugs.gnu.org/15361

> (tho I seem to remember that Glenn implemented some kind of
> Message-ID/In-Reply-To based system to try and correct this, so maybe
> it'll work).

I did implement that, but while it works ok for "normal" email
conversations, it doesn't for git send-email, as explained in the above
bug.

> But you can send a first message to bug-gnu-emacs@gnu.org and then send
> threaded messages to the corresponding NNN@debbugs.gnu.org address.

Yes, that is what I would recommend.



  parent reply	other threads:[~2014-06-02 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  8:35 Sending multiple patches Michal Nazarewicz
2014-06-02 13:17 ` Stefan Monnier
2014-06-02 13:24   ` David Kastrup
2014-06-02 16:15     ` Stefan Monnier
2014-06-02 17:58       ` Yuri Khan
2014-06-02 15:47   ` Glenn Morris [this message]
2014-06-02 18:33   ` Michal Nazarewicz
2014-06-02 19:11     ` Stefan Monnier
2014-06-03  6:28       ` Michal Nazarewicz
2014-06-03 13:25         ` Stefan Monnier
2014-06-07 17:28           ` Michal Nazarewicz
2014-06-08  1:26             ` Stefan Monnier
2014-06-07 15:05         ` Herring, Davis
2014-06-02 19:03   ` Michal Nazarewicz
2014-06-03  0:00     ` Stefan Monnier

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=ygbnubgvo8.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=mpn@google.com \
    /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).