From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: master f962c5d 2/2: Add patch-sending instructions to git-workflow
Date: Thu, 10 Sep 2015 12:14:40 -0400 [thread overview]
Message-ID: <l7y4ges13j.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1ZZyPP-0005jV-3j@vcs.savannah.gnu.org> (Paul Eggert's message of "Thu, 10 Sep 2015 09:44:47 +0000")
Paul Eggert wrote:
> +git send-email --to=bug-gnu-emacs@gnu.org 0001-DESCRIPTION.patch
I would like to discourage this usage because when there's more than one
patch in a sequence, it will create a separate report for each.
(http://debbugs.gnu.org/15361)
parent reply other threads:[~2015-09-10 16:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1ZZyPP-0005jV-3j@vcs.savannah.gnu.org>]
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=l7y4ges13j.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eggert@cs.ucla.edu \
--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.