From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: qtwenengine anybody? Date: Mon, 13 Jan 2020 15:26:51 +0100 Message-ID: <87imlfqvo4.fsf@ambrevar.xyz> References: <5955729d-ef57-ffb8-feb8-36a9f53658a2@crazy-compilers.com> <87d0clpbt6.fsf@gmail.com> <87y2v7e0g4.fsf@ambrevar.xyz> <87v9qb56gg.fsf@gmail.com> <87sglfotvj.fsf@ambrevar.xyz> <87o8w354m5.fsf@gmail.com> <87blrod2so.fsf@ambrevar.xyz> <878smsd2pe.fsf@ambrevar.xyz> <87mub7krlq.fsf@gmail.com> <87tv5e9acb.fsf@ambrevar.xyz> <87o8vmn6an.fsf@elephly.net> <87zhf2c5jy.fsf@gmail.com> <87lfql7k9w.fsf@elephly.net> <87d0bw2xtj.fsf@devup.no> <871rsccdq8.fsf@gmail.com> <871rsbxdzt.fsf@gmail.com> <878smdzydh.fsf@devup.no> <87zhetj3hv.fsf@ambrevar.xyz> <87muareide.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:37370) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ir0gD-0003io-0j for guix-devel@gnu.org; Mon, 13 Jan 2020 09:26:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ir0gB-0005nL-JB for guix-devel@gnu.org; Mon, 13 Jan 2020 09:26:56 -0500 In-Reply-To: <87muareide.fsf@gmail.com> 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-mx.org@gnu.org Sender: "Guix-devel" To: Mike Rosset Cc: GNU Guix maintainers , guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Mike, > I've have sent some patches to an open bug #38148 in regards to > qutebrowser being outdated. I'm hoping this will help test out > qtwebengine and close that bug. Two birds with one stone :) Qutebrowser 1.9.0 works now, great job! I've reviewed those patches; fix the few nits and I'll merge. > On second thought maybe I should have emailed them to > guix-patches@gnu.org. Let me know if that's better for reviewing. If you think the bug title is relevant, then it's the right thing to do. That said, it seems that you've sent the first patch twice. To clarify, this is how you should proceed to send patches to debbugs: 1. Send the first patch only. If you send with "git send-email", you should see the message ID in the output. 2. Send all other patches by using the "--in-reply-to=3D$ABOVE_MESSAGE_ID" option. Make sure the patches are in the right order on the command line. Example: git send-email --to=3D38148@debbugs.gnu.org \ --in-reply-to=3D'<20200113103304.9093-1-mike.rosset@gmail.com>' \ 0002-patch-foo.diff 0003-patch-bar.diff =20=20 Hope that helps! =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl4cfisACgkQm9z0l6S7 zH8q8Qf/TX7lka9trQTO9VWlVn01zk1pfx+844Azn0TCoBGeeoz3Z6SXXBW2XqGk t08TcdXdKJfPDDq+SUAn8tdkDOWxwS0CPDON2BHVVQPEKBqXJyzvcWwNyfp6KWpD Qcyv7C30ZhrveyuLj1J1lMpCDW7p5JL5bsJwFQ+osfsUu7HAJfyDe9FKIUNsz8lE 1qEntL+njBpq2GNVDRypmAHEtuzkvBZByoewZUVosbceABhZlHXJVr8ARrHAKzab OpxA96c79mYvB1oaVLpFWvG35jHAgabyunLeuuajouAsnwf4tTeMkhtcf9M1y2jd KdP1q5xWoMFpXqRHpnkiZL4WrgDyUQ== =fF1A -----END PGP SIGNATURE----- --=-=-=--