From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Patchwork + automated checking and testing of patches
Date: Wed, 07 Nov 2018 23:00:52 +0100
Message-ID: <8736scsg2z.fsf@gnu.org>
References: <87h8h29z2j.fsf@cbaines.net> <87pnvostyl.fsf@gnu.org>
	<871s844oh0.fsf@cbaines.net> <87sh0e2v7v.fsf@gnu.org>
	<87y3a4hgu3.fsf@cbaines.net>
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]:59111)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1gKVsd-0006t2-Gi
	for guix-devel@gnu.org; Wed, 07 Nov 2018 17:00:56 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1gKVsc-00055Y-7S
	for guix-devel@gnu.org; Wed, 07 Nov 2018 17:00:55 -0500
In-Reply-To: <87y3a4hgu3.fsf@cbaines.net> (Christopher Baines's message of
	"Wed, 07 Nov 2018 18:40:04 +0000")
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: Christopher Baines <mail@cbaines.net>
Cc: Guix-devel <guix-devel@gnu.org>

Hi Christopher,

Christopher Baines <mail@cbaines.net> skribis:

> So, I was trying to work out how to update a series of patches, and
> asked on the Patchwork mailing list [1], and discovered there's actually
> another codebase with different features [2]. This Patchwork-FDO fork
> does have a page that just displays series [3].
>
> 1: https://lists.ozlabs.org/pipermail/patchwork/2018-November/005674.html
> 2: https://gitlab.freedesktop.org/patchwork-fdo/patchwork-fdo/
> 3: https://patchwork.freedesktop.org/project/intel-gfx/series/?ordering=
=3D-last_updated

Interesting.

> In terms of patch tracking, I'm thinking on Patchwork and Debbugs
> independently, while I think it would be possible to integrate the two,
> Patchwork has the tracking capabilities of Debbugs, so if Patchwork ever
> becomes useful for automated testing of patches, it would probably
> remove the need to use Debbugs to track patches (not actual bugs and
> issues).

Yes maybe, though Debbugs has features that make it attractive to me
(SOAP interface and Emacs interface, properties attached to =E2=80=9Cbugs=
=E2=80=9D, etc.)

> Anyway, I think the next thing to try and do is get something
> (Patchwork, Patchwork-FDO, Debbugs/issues.guix.info) triggering tests
> for patches. I still need to compare the two Patchwork codebases to see
> if they differ in this respect.

Sounds like a plan!

Thanks,
Ludo=E2=80=99.