From: Philipp Stephani <p.stephani2@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Seeking a "Patch Champion"
Date: Thu, 28 Apr 2016 19:30:50 +0000 [thread overview]
Message-ID: <CAArVCkTNp0j_U3R0i0oxzDf6uxqjdmNL2wd32kEXZ3NmMjYAAg@mail.gmail.com> (raw)
In-Reply-To: <m2d1pgxbp9.fsf@newartisans.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
John Wiegley <jwiegley@gmail.com> schrieb am Sa., 23. Apr. 2016 um
23:22 Uhr:
> To assist this effort, I've connected our mailing lists with a service
> running
> on my own VPS (for now) called "Patchwork"[1]:
>
> http://patchwork.newartisans.com/
>
> Every patch sent -- either on emacs-devel or bug-gnu-emacs -- is captured
> by
> this server and assigned a ticket number.
>
Great, thanks! One question though: Is the patch list expected to be
complete? For example, I can't seem to find my patches in the interface.
See, for example, the patch attached to
https://lists.gnu.org/archive/html/bug-gnu-emacs/2016-04/msg00706.html:
I've searched both patch sets for the bug number, yet I can't find the
patch.
[-- Attachment #2: Type: text/html, Size: 1197 bytes --]
prev parent reply other threads:[~2016-04-28 19:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 21:22 Seeking a "Patch Champion" John Wiegley
2016-04-23 21:45 ` Dmitry Gutov
2016-04-23 21:54 ` John Wiegley
2016-04-25 19:50 ` Dmitry Gutov
2016-04-25 19:59 ` Dmitry Gutov
2016-04-25 21:29 ` John Wiegley
2016-04-25 21:35 ` Dmitry Gutov
2016-04-26 14:27 ` John Wiegley
2016-04-25 11:29 ` Nicolas Petton
2016-04-25 17:37 ` John Wiegley
2016-04-25 18:48 ` Nicolas Petton
2016-04-25 19:17 ` John Wiegley
2016-04-25 19:28 ` John Wiegley
2016-04-25 16:40 ` Lars Magne Ingebrigtsen
2016-04-25 18:11 ` Karl Fogel
2016-04-25 18:14 ` Lars Magne Ingebrigtsen
2016-04-25 19:22 ` Karl Fogel
2016-04-25 19:51 ` Dmitry Gutov
2016-04-25 20:27 ` Dmitry Gutov
2016-04-25 20:37 ` Lars Magne Ingebrigtsen
2016-04-25 20:51 ` Dmitry Gutov
2016-04-25 21:14 ` Lars Magne Ingebrigtsen
2016-04-25 21:34 ` John Wiegley
2016-04-25 22:04 ` Lars Magne Ingebrigtsen
2016-04-25 23:44 ` Lars Magne Ingebrigtsen
2016-04-26 6:32 ` Andreas Röhler
2016-04-26 14:30 ` John Wiegley
2016-04-26 15:04 ` Nicolas Petton
2016-04-26 20:24 ` Dmitry Gutov
2016-04-26 21:01 ` John Wiegley
2016-04-27 6:16 ` Eli Zaretskii
2016-04-27 14:40 ` Lars Magne Ingebrigtsen
2016-04-27 15:31 ` Nicolas Petton
2016-04-27 15:49 ` Lars Ingebrigtsen
2016-05-02 7:55 ` Nicolas Petton
2016-05-02 20:55 ` John Wiegley
2016-05-02 21:54 ` Lars Ingebrigtsen
2016-05-03 7:58 ` Michael Albinus
2016-04-28 19:30 ` Philipp Stephani [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=CAArVCkTNp0j_U3R0i0oxzDf6uxqjdmNL2wd32kEXZ3NmMjYAAg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--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 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).