From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Patchwork
Date: Tue, 10 May 2016 15:56:59 +0200
Message-ID: <idjmvny3tjo.fsf@bimsb-sys02.mdc-berlin.net>
References: <87pot4ab2a.fsf@gnu.org>
	<idjh9eg5w21.fsf@bimsb-sys02.mdc-berlin.net>
	<877ffch32a.fsf@gnu.org> <20160510060233.GD1075@debian-netbook>
	<87lh3ighr6.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40899)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Ricardo.Wurmus@mdc-berlin.de>) id 1b0boH-0008BO-Cy
	for guix-devel@gnu.org; Wed, 11 May 2016 17:36:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Ricardo.Wurmus@mdc-berlin.de>) id 1b0boD-0001hQ-0z
	for guix-devel@gnu.org; Wed, 11 May 2016 17:36:48 -0400
In-Reply-To: <87lh3ighr6.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>


Ludovic Court=C3=A8s <ludo@gnu.org> writes:

> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> On Mon, May 02, 2016 at 05:50:21PM +0200, Ludovic Court=C3=A8s wrote:
>>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>>>=20
>>> > I=E2=80=99ve submitted a patch to the mailing list (this time inlin=
e with =E2=80=9Cgit
>>> > send-mail=E2=80=9D) and it appeared in the list.  Is there any way =
for us to
>>> > mark patches as committed via email (e.g. by commenting with someth=
ing
>>> > like =E2=80=9CPushed as cabba9e.=E2=80=9D) or does patchwork figure=
 this out
>>> > automatically?  Or can only people with an account change the statu=
s,
>>> > and only on the web interface?
>>>=20
>>> That=E2=80=99s a good question!  I *think* Patchwork can find out by =
itself by
>>> looking at the repository, but I don=E2=80=99t know exactly.  We=E2=80=
=99ll see.  :-)
>>>=20
>>> Ludo=E2=80=99.
>>>=20
>>
>> The connman patches I've already committed are still listed as new on =
patchwork,
>> and I didn't see a way to manually mark them as done.
>
> Apparently Patchwork can sometimes (I=E2=80=99m not sure exactly when)
> automatically determine whether a patch has been applied; in other
> cases, one must manually mark the patch as applied in the Web interface=
.
> :-/

We also have cases where patches were retracted (such as the ones for
=E2=80=9Cr-mass=E2=80=9D and =E2=80=9Cr-survival=E2=80=9D).  It would be =
convenient if the submitter
could do this by sending email instead of having to use the web
interface.

Since this patchwork instance is not hosted by ourselves I suppose we
cannot just patch it to make it work like that.

~~ Ricardo