From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 0/2] Tcsh update for core-updates Date: Fri, 24 Feb 2017 11:55:11 -0500 Message-ID: <20170224165511.GA28458@jasmine> References: <20170224094038.nlnm34po7hyuu5y5@wasp> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53737) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1chJ9J-0001MX-Dx for guix-devel@gnu.org; Fri, 24 Feb 2017 11:55:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1chJ9F-0007ir-Cm for guix-devel@gnu.org; Fri, 24 Feb 2017 11:55:17 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:58032) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1chJ9F-0007id-6x for guix-devel@gnu.org; Fri, 24 Feb 2017 11:55:13 -0500 Received: from localhost (c-73-188-17-148.hsd1.pa.comcast.net [73.188.17.148]) by mail.messagingengine.com (Postfix) with ESMTPA id 3222D24323 for ; Fri, 24 Feb 2017 11:55:12 -0500 (EST) Content-Disposition: inline In-Reply-To: <20170224094038.nlnm34po7hyuu5y5@wasp> 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: guix-devel@gnu.org --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 24, 2017 at 09:40:38AM +0000, ng0 wrote: > On 17-02-24 03:16:43, Leo Famulari wrote: > > This updates tcsh to the latest upstream version. >=20 > some weeks ago I worked on this. Put a significant amount of time into > the update, waited for replies and asked upstream about the cdhome > issue as I don't understand tcsh syntax that much. > This is exactly why I don't think email is the perfect tool for project > work. There is no reminder to tell you someone already worked on this, > no interactive search unless you have it yourself. > It would be good if you could search the archive next time and tell me > to rebase or redo it on core-updates. I understand that is frustrating, but I did read that discussion before starting to work on my patch. Also, Tobias worked on it last August. In both cases, there were some questions about the changes, and then the patch authors stopped working on the patch. Now, tcsh is blocking core-updates, so I decided to try updating tcsh. It's hard to take a pre-existing patch from somebody else and try to figure out what parts are necessary, which parts can be discarded, which parts should be adjusted, et cetera. Especially for a complicated package update that requires adjusting patch files. It's a lot easier to try the upgrade from scratch and fix problems as I find them. --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAliwZW8ACgkQJkb6MLrK fwg2HRAAokP7NKe1DaKdCo2HqUFb6MO6TeQWjg5kwQkWSDzKUDBKHoro6JZAfqSY y6s2oQcdYHjprOEv4QNTo8uPFMWnZnNLPFwsA0d9A+kHndJWVFngvdiHs/vaIx67 Sdgfj+jaVJFWpfBDcs2r9X/uABnCtEpviU7nC+xvwyRT7xP2ycv2FIBJQbngaMd1 tw/IwEh1rsvjwsQYkXI6GeoScYDpJx2+L9ge1/zfh1sXeSXmQtClM1C/MsPfCbHD Ppx6GU2dLq1rQpIGuqoRaxyfpImDFmroqr7p6hypT5fVjZdyZZngRiRvM79vI63u VxE3J/mZt0NIyxYun4HYyIREm6+RXSF3eVzGNyzpN9Bb8hwbo2L1R5wTG2Rg//kl sOFxe7baRPXXthlyNeoDfN2RbZGj/ft1Li5VfJrFKbP1ERI118mWIXGfGtp3J4+E +50hBp3N+XqOaOQRu6bGdTkHjxbFOHC28ahSNucJVgbnI1Jzjnyio3F/NAird/TJ bxhj/TqEsRSo5QilImLTYWq80Phr97K/C1L9hrIPtlFnQqMRQtevnoYYRUA6TrGk Tj0P9j4GFHoGI1nHKMRoT+bvMckjMlc+Xqnx43LldaI99Zx6oHD8QxT/wYVSWbIE lzWtedRQaV0dI7YP4OIZvgBD8hj7LahOTxBmUg0EvvmFdIL65Yk= =Kwj3 -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu--