From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: workflow Date: Sat, 6 Jan 2018 22:56:16 +0000 Message-ID: <20180106225616.qsm7ac72gcg3nkis@abyayala> References: <20180104101213.d4gcgqihxu6d77eb@abyayala> <877esur5sm.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oloqo7azdodhpg7v" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45940) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eXxOF-0003qo-Rd for guix-devel@gnu.org; Sat, 06 Jan 2018 17:56:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eXxOD-0004AF-8V for guix-devel@gnu.org; Sat, 06 Jan 2018 17:56:35 -0500 Received: from aibo.runbox.com ([91.220.196.211]:50094) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eXxOD-00047A-0T for guix-devel@gnu.org; Sat, 06 Jan 2018 17:56:33 -0500 Content-Disposition: inline In-Reply-To: <877esur5sm.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.org@gnu.org Sender: "Guix-devel" To: Chris Marusich Cc: guix-devel --oloqo7azdodhpg7v Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Chris Marusich transcribed 1.6K bytes: > ng0 writes: >=20 > > You can stash those po/* files, it's the first thing I do if I ever > > happen to work on a complete new checkout. >=20 > Do you stash JUST the po files? Yep. And I never stash apply them back. There's a stash of the po that I ha= ve for about almost as long as I contribute to Guix. > I have often found these po files very > annoying while trying to make changes to Guix and test locally. I think > that if I do "git stash" and later "git stash pop", it updates the > timestamps of many files, so "make" rebuilds many, many things that it > really doesn't have to. >=20 > Beyond doing "git checkout po" are there any other ways to deal with > these po files that won't negate make's incremental build feature? >=20 > --=20 > Chris Maybe we could add them to .gitignore, but I haven looked into the buildsystem for some time, if that would affect for example make dist. But as long as you don't run make dist you could have them in a .gitignore. --=20 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys WWW: https://n0.is/a/ :: https://ea.n0.is --oloqo7azdodhpg7v Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlpRVBAACgkQ4i+bv+40 hYjPxhAAqhFRLNqoS+WzSi4b0g7Z6iWKjUJyM08uALtGDGQ2sEKDFYoSmvK8JW4S +aJ+zXHloED6h5+dEYX0Fqfd5RnO5NHsCCesdLSSXtOCLV6VFjfIyxJ17hmL2BRQ wVJvOE3wI9l1c4ri1IapC1YX0wj3tJGI6dMOIDPwazV/ENvPgEBxNgKR10RuFu69 Qv87hqd1HJHFEuePUW0Tb6/Y7a8Fi1nXBEJ1Ll1+UgseLhj+1xu3iaURSPdwentp oSVKv5vY/OgaOR9qZQyy3X1no8zQn6iV5FIid10+n3UeOyWbhh9PDmjRnnJxiUFK ahB7o750auFhl70Zse8DVKZcd/Az0gZ1QxdM3BLwiHCS5JOtcEfyqAnV3VgnwTIT 8zB0mHNDZler81pEdl7MpXSnuI2OYkt576NjdAvRgodud0S1yxFu5pTLYvB8uGLE cnTIaJ8/nOpodflU5uPEUfDSXiQPbJezIy7BOs+K0i6Q53482Uc+sU0RoTKDL9he IzxvqhNJEoBiUQFJ7745+uFxCvzssgVQmLTI88dVCQgzr0hEecTvVC/nzbSBel6X m1vhulxid6e7S0B7D+9njYrayyMxwKMMivaRjJSl5kOEBuZqRt2km+vbzlttH4jH NYhlMR505NP3yPPCs+G3gSlJc2fVLkAXnn784m9u1cmPZNfEZfc= =JG+g -----END PGP SIGNATURE----- --oloqo7azdodhpg7v--