From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Re: Seeking a "Patch Champion" Date: Thu, 28 Apr 2016 19:30:50 +0000 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2432af416170531909050 X-Trace: ger.gmane.org 1461871881 7647 80.91.229.3 (28 Apr 2016 19:31:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 28 Apr 2016 19:31:21 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 28 21:31:14 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1avreb-0000YM-MC for ged-emacs-devel@m.gmane.org; Thu, 28 Apr 2016 21:31:13 +0200 Original-Received: from localhost ([::1]:50733 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avrea-0006Yv-PI for ged-emacs-devel@m.gmane.org; Thu, 28 Apr 2016 15:31:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45220) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avreV-0006VR-8W for emacs-devel@gnu.org; Thu, 28 Apr 2016 15:31:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1avreQ-0000ua-U7 for emacs-devel@gnu.org; Thu, 28 Apr 2016 15:31:07 -0400 Original-Received: from mail-lf0-x22a.google.com ([2a00:1450:4010:c07::22a]:33745) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avreQ-0000tG-2h for emacs-devel@gnu.org; Thu, 28 Apr 2016 15:31:02 -0400 Original-Received: by mail-lf0-x22a.google.com with SMTP id y84so95547121lfc.0 for ; Thu, 28 Apr 2016 12:31:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2G0+rtO0yV4DRF+IahdXKjgci18tzJS/YeQ7YjB9iLo=; b=ocQJVfN/ncjZXr4DmK14OUKBNsBhlk3mbvZBfdi8uShAMxoGFzoRI81ZT3L/Snf0bl cZg8I/Wf4iz2kuPAPbWmW4dlimGwPfWQnldPim0m/mT3jrpGINONp0xDdpFMK+55JM4D IuSSpoeJfxTA6TOtE2+t3KwgSr0uetjXwfGCVaOPBBZRw1LGY2t/IkLBJdzVgdJp4hHD GI2OsbCK1Hb9ySw6ifPFXmr4lE6kdcXeHBcFU8Pl9RX98i2kP10S04+wUHzEBGwNlxUv H1t4pZn737d5UWpklHbg21wZVVyL91zn5EFonX2ZfvzzV/coXgEKhFsSPMeUGJ0Blh8p q09Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2G0+rtO0yV4DRF+IahdXKjgci18tzJS/YeQ7YjB9iLo=; b=eRLkEkrVHiZg5wmF1pO7Te/RfYfHeWq0e6ZwfAhTM6iX4unwzF2UPYzvFTjfMovARw RJqbNgpVdO/DGMk41dDAKDPm7h0t6ZuxUmdsye+6vzsMHWBg0DPfHVjqGkTSvg/O/MUd 1RGZJF/scO8xO0y3qvqH4kEJd8CMXHhKHoUTTWOfGYQJxsqlKYRZ6kyp0dcTGAzVIi1t vMiH7oPJFTEZjuoy+bAvw3o1I4IbIJ/ZRcRUovU/QhcctfhNQn8hCUBUnacgHiiva7k4 C8lH3GCezHocqeHKITp72VwQ+qevbJzJUiyGLXW6PuxIZauaI7F2Xz9qJQDaD+nPx5xa X9HA== X-Gm-Message-State: AOPr4FXiT+nsPQ+D8UWL9RCDOwAkCfIo8yGMmVQMUDQ5EA+fZzwstP8kk8feDWJ8Wt5rjOp0fAZHrSo0GiOCiQ== X-Received: by 10.112.167.228 with SMTP id zr4mr6924493lbb.74.1461871860518; Thu, 28 Apr 2016 12:31:00 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c07::22a X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:203402 Archived-At: --001a11c2432af416170531909050 Content-Type: text/plain; charset=UTF-8 John Wiegley 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. --001a11c2432af416170531909050 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


John W= iegley <jwiegley@gmail.com>= schrieb am Sa., 23. Apr. 2016 um 23:22=C2=A0Uhr:
To assist this effort, I've connected our mailing lists = with a service running
on my own VPS (for now) called "Patchwork"[1]:

=C2=A0 =C2=A0 http://patchwork.newartisans.com/

Every patch sent -- either on emacs-devel or bug-gnu-emacs -- is captured b= y
this server and assigned a ticket number.

<= div>Great, thanks! One question though: Is the patch list expected to be co= mplete? For example, I can't seem to find my patches in the interface. = See, for example, the patch attached to=C2=A0https://lists.gnu.org/= archive/html/bug-gnu-emacs/2016-04/msg00706.html: I've searched bot= h patch sets for the bug number, yet I can't find the patch.
--001a11c2432af416170531909050--