From: John Wiegley <jwiegley@gmail.com>
To: Bill Wohler <wohler@newt.com>
Cc: mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: MH-E manual patch
Date: Mon, 13 Jun 2016 12:49:21 -0700 [thread overview]
Message-ID: <m2inxceuny.fsf@newartisans.com> (raw)
In-Reply-To: <87zir7qexz.fsf@olgas.newt.com> (Bill Wohler's message of "Mon, 30 May 2016 16:55:04 -0700")
>>>>> Bill Wohler <wohler@newt.com> writes:
> Is there anything I need to do to address its entry here?
> http://patchwork.newartisans.com/patch/624/
Typically you'd manipulate the metadata for the patch in the list for that
group.
However, it looks like the consensus is that we'll be keeping patch management
within debbugs for now, by using queries to determine which open bugs have
related patches.
The main thing we need to do now is to ensure that every patch sent directly
to emacs-devel is copied to a new issue.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
next prev parent reply other threads:[~2016-06-13 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8737q1rz0z.fsf@olgas.newt.com>
2016-05-02 20:58 ` MH-E manual patch John Wiegley
2016-05-30 23:55 ` Bill Wohler
2016-06-13 19:49 ` John Wiegley [this message]
2016-05-02 2:09 Bill Wohler
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=m2inxceuny.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mh-e-devel@lists.sourceforge.net \
--cc=wohler@newt.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 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.