From: Leo Famulari <leo@famulari.name>
To: Brett Gilio <brettg@posteo.net>
Cc: 34600@debbugs.gnu.org
Subject: [bug#34600] [PATCH 1/5] gnu: emacs-which-key: Update to 3.3.1.
Date: Thu, 21 Feb 2019 15:30:38 -0500 [thread overview]
Message-ID: <20190221203038.GA19893@jasmine.lan> (raw)
In-Reply-To: <87ef81lybo.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
On Thu, Feb 21, 2019 at 01:46:03PM -0600, Brett Gilio wrote:
> You're going to have to be more specific. Do all patch series go under a
> single bug number?
If the patches are related, or depend on each other, then they should be
mailed to the same bug number. Otherwise it's more difficult to review
the patches.
You can send an intro email to <guix-patches@gnu.org>, wait for the
number to be assigned, and then send the patches to that numbered
address <NNN@debbugs.gnu.org>.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-21 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 2:13 [bug#34600] [PATCH 1/5] gnu: emacs-which-key: Update to 3.3.1 Brett Gilio
2019-02-21 19:30 ` swedebugia
2019-02-21 19:46 ` Brett Gilio
2019-02-21 20:30 ` Leo Famulari [this message]
2019-02-21 21:30 ` Brett Gilio
2019-02-22 8:28 ` swedebugia
2019-02-24 3:10 ` bug#34600: " 宋文武
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=20190221203038.GA19893@jasmine.lan \
--to=leo@famulari.name \
--cc=34600@debbugs.gnu.org \
--cc=brettg@posteo.net \
/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/guix.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.