From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cseug-0000c4-19 for guix-patches@gnu.org; Mon, 27 Mar 2017 20:23:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cseuc-0007bR-QU for guix-patches@gnu.org; Mon, 27 Mar 2017 20:23:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:49798) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cseuc-0007bK-HR for guix-patches@gnu.org; Mon, 27 Mar 2017 20:23:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cseuc-00088q-Bu for guix-patches@gnu.org; Mon, 27 Mar 2017 20:23:02 -0400 Subject: bug#26277: [PATCH 1/1] gnu: webkitgtk: Update to 2.16.0. Resent-Message-ID: Date: Mon, 27 Mar 2017 20:22:56 -0400 From: Leo Famulari Message-ID: <20170328002256.GA24075@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="OXfL5xGRrasGEqWY" 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" To: Marius Bakke Cc: 26277@debbugs.gnu.org --OXfL5xGRrasGEqWY 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. Good idea, especially since the change is not mentioned in NEWS. I added some links to the commit message and pushed as c38685524956a9451ce254da80f6819be53ead6c. --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAljZrOAACgkQJkb6MLrK fwiMAg/7BtYQaZGLrJCZSEtWi9d58oPNPF96Q8FcrB3rVh2MM3oSLRCLfq97Sndj RQxMFPWhlmGqSBq8/T4KW4sMvZeH5Nj78UYK2PyNlKk/1/q9bTOP9iHZVTzl1WUz +n/JDytmUjtL6v7skKOtXeTfFkCELzKyItUJkzcJCJ7DNYPenQDKYiBdKxd0GCsz yiteWKUnrP59fdM1KE4ybXV23p7w4g9ljCTcwl17B4zZapCiJRIQLD0MHZqimpdv hhAtCduC72+ckaDjpZTb5Qyv44UPJf3YfQkLSVp1Qdp15tH8e9hp/YvLwzdg/OiV L95K0cYxikpFjZl1v1BDZTT0MO3V32OENBTE/OezR8OH1sji40srgjiNDo57q4eP GuSOGwsVa9tV9RMNvZNuDsWvWWaGAuSEZ3+Xk1z0ZTMsf4qK077ndeOzEAcRTrd5 /jVJyRjn7d+gZ0tE9cAVa6cQo3FfcRf3M8NRqdSfSA5+BvSl/pRkleWNzVG4rMQX s6wS6MeXhXwCEIipr3pwn3b8Jbsx5SBuKFzL/lhZueaRuQ5/Q0J+ovkRDmHciePS aDw0w7FppBZR3mYDIgkyuyKPkWl6+Qjt43BJwIvmN5HYvpo2rSfLFdBCx/5nMvNK Bdtcch4mjT6wJ7reqcy1mxxSFe6Nbg+dQn5JHyk6WqlaJ5eg67U= =OXWF -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY--