From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36305) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cseve-0000gi-CF for guix-patches@gnu.org; Mon, 27 Mar 2017 20:24:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1csevb-0007ty-7n for guix-patches@gnu.org; Mon, 27 Mar 2017 20:24:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:49814) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1csevb-0007tn-3v for guix-patches@gnu.org; Mon, 27 Mar 2017 20:24:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cseva-0008BL-Uk for guix-patches@gnu.org; Mon, 27 Mar 2017 20:24:02 -0400 Subject: bug#26277: [PATCH 1/1] gnu: webkitgtk: Update to 2.16.0. Resent-To: guix-patches@gnu.org Resent-Message-ID: Date: Mon, 27 Mar 2017 20:23:33 -0400 From: Leo Famulari Message-ID: <20170328002333.GB24075@jasmine> References: <87shlyuzjo.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="E39vaYmALEf/7YXx" Content-Disposition: inline In-Reply-To: <87shlyuzjo.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" Cc: 26277-done@debbugs.gnu.org --E39vaYmALEf/7YXx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 28, 2017 at 12:26:19AM +0200, Marius Bakke wrote: > Leo Famulari writes: >=20 > > * gnu/packages/webkit.scm (webkitgtk): Update to 2.16.0. > > [inputs]: Replace gnutls with libgcrypt. >=20 > LGTM. I trust your judgement on this, so I don't think posting it here > is necessary (not that I'm in charge though! :P). I think most of us > read the commit history anyway and would raise questions as necessary. >=20 > But since we're here, if there are blog posts, release notes, or other > rationale explaining why this change is necessary, it could be good to > include in the "message area" of a commit, IMO. Closed! --E39vaYmALEf/7YXx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAljZrQUACgkQJkb6MLrK fwjQKA//fy890PT4sa4dYubs36yZqC8N8WMc+B2CuE2dKiRT4TNGQtujNZgzUNet 74vMDUjM8MznHlwUetiA2v3fedufFHhuRLngBAgoZD1jN5KT8z5B8yJzz+zS4Qoe NBl4Je6aufB8ARZ+WL+IfhGms7XA8ivRAJYQchsivWTN+tLTFTMThvbVIyUfGUwt GaSah4UwhHpblVji3jTj55EPVBEryUk1iQTjkj2ROmrLt6hXcWCcAKEQgVquSQ6w Uc6xm6wLJRE5PRfwBE9hCvOiZECv3RPmZvMAQF8PKL6iizfH1y93pCKeIjmJMDvs SFuPV0tJAKmJ3y5q1avSpdQKJE6PJBraXqS8enXhB1TlTkDbRdwxS5SDhrPViwoF bMPdn4ANzsyOPNeZyX1Qt6B1CgC0zh1ZBuO+r96JtG+S/biGC2x/RRARLkG5bDxd ZcrgA4LMYMtilclDFGr4/c4HOzr3gVuKXzy4xT60T/aNOJ25/bWrdqvyfP1Z11Mq HgTaIcqI+/DDk91sxrPzn8kRi83u29uHUdh9pNTtb5K4cfLIRDGXlMf0UiFfGADV Hqf55q7Ex6B00cnRyoGZQ7K2HMDAlZu6TCFHlBmdRYP9ZzyICxPZBAFEkv62g9F2 XbTzR1eQcH97vB28mYOzA8iDZlRcQ/cBhq6lal9MC/JgJzID5/Q= =C4UA -----END PGP SIGNATURE----- --E39vaYmALEf/7YXx--