From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Patchwork + automated checking and testing of patches Date: Wed, 07 Nov 2018 18:40:04 +0000 Message-ID: <87y3a4hgu3.fsf@cbaines.net> References: <87h8h29z2j.fsf@cbaines.net> <87pnvostyl.fsf@gnu.org> <871s844oh0.fsf@cbaines.net> <87sh0e2v7v.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gKSkl-00031L-Ig for guix-devel@gnu.org; Wed, 07 Nov 2018 13:40:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gKSkZ-0000Rd-Mt for guix-devel@gnu.org; Wed, 07 Nov 2018 13:40:29 -0500 In-reply-to: <87sh0e2v7v.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Hello! > > Christopher Baines skribis: > >> Ludovic Court=C3=A8s writes: > > [...] > >>> Back when we tried, it had a couple of shortcomings: >>> >>> 1. It would not automatically detect which patches have been merged; >>> >>> 2. It would not present patch series correctly. >>> >>> From what you write it looks like #1 has been fixed, but the web >>> interface suggests that #2 isn=E2=80=99t quite fixed yet, is that corre= ct? >> >> On the detecting merged patches, that's definately working for some >> patches though. I don't fully understand what criteria it's using >> though, as it's comparing the commits that come through to the master >> branch, and I bet it's possible to confuse it a bit by tweaking patches >> before pushing them. >> >> Regarding patch series, I don't know much about the specifics of this, >> and I don't know much about Patchwork, but just comparing a few patches >> on the older version [1], and the newer version [2], it looks like it's >> better. Take this patch [3], it's part of a series, but you can't >> tell. However, with this patch [4], you can see the series and related >> patches towards the top of the page, and also a link to download the >> whole series as an mbox. How does this look to you? > > It looks better than the old Patchwork version, but I think > still leaves > a bit to be desired. For instance, it shows every message, even for > series. > > At this point I find > clearer and less cluttered, though it needs some improvements (e.g., > most-recent-first sorting, listing all the open issues, etc.), which I > think should be relatively easy to do. Also, it is directly linked to > Debbugs and its notion of issues and associated properties (bug number, > owner, status, tags, etc.), which is good IMO. > > WDYT? 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 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). 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. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAlvjMYVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XcR1Q//ZE4rV5YysX3TA1QBq9I4bg1ekXYAcdIbtIRXHqAmYejQcPszga2X/ahn GgTufQ0axUGVY6itM8kHOOuONqdlS2Xk7Ak7aUjBhkY7XfkuWv07rKbr52fIz/2C aIFZF+aA7QFrMbpttmhV26RkEjrfgI2OtQJ5DXx8qSAulxkTO/s1jd/Jc8J3H5yM B7Enl6uVMRxyQPtRqJ/OYOK701V89RaQwKZvyNjOtuwk45wydlh04xwNthJ10H2X kGFAs4fL1nYDhyidUyQbnw/Osi0PCSRTGFPRuKxrVqCBmwWav3NTB9/amgXGLUqv QZ0dTb9uaygEYI5aQigiMKAluf/oNq64/Iy7AZQaNE1TKWPj0lLQKQGLeQ1xj76V ySV4sOXCY3u8b3EbG4XuvlGPjoIpYXQEcrGgR8fXIpIHBu38QgNBYdJXl/G1zrMf 8CDGlt52w8CZtSzV/hD9N1gqmrido8shFfsHLAMgqM/AxM+pz7vZgMv5MBH48FyC GDpKvCTLdm2VAnoIKvhxJIFgEe/56C+O8PvQNUaF/Hicvfp5lm3pB1EDD1ZRCcxX eTeT5IRaM2BRxmeymjO5dlw9UunHUD0KRgJvyQ/fdq2lL6D07ODW7uy2zCOGzGcg fyIqdEH5aq5pL9trcFTM+3Cg5NwY28x3UVWGhgdZ0i7PC0rJGA0= =Bjk3 -----END PGP SIGNATURE----- --=-=-=--