From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Should these files ignored? Date: Wed, 27 May 2015 17:04:08 +0200 Message-ID: <87zj4qhxjr.fsf@gnu.org> References: <87ioblvw3y.fsf@163.com> <87pp5o1ijz.fsf@gnu.org> <20150526154532.GA27664@thebird.nl> <87mw0rkr03.fsf@gnu.org> <874mmzuik5.fsf@T420.taylan> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56211) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxcsS-000778-67 for guix-devel@gnu.org; Wed, 27 May 2015 11:04:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YxcsP-0002g1-0B for guix-devel@gnu.org; Wed, 27 May 2015 11:04:16 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52403) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxcsO-0002fx-TZ for guix-devel@gnu.org; Wed, 27 May 2015 11:04:12 -0400 In-Reply-To: <874mmzuik5.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Tue, 26 May 2015 23:37:14 +0200") 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Taylan Ulrich =?utf-8?Q?=22Bay=C4=B1rl=C4=B1?= =?utf-8?Q?=2FKammer=22?= Cc: guix , Feng Shu taylanbayirli@gmail.com (Taylan Ulrich "Bay=C4=B1rl=C4=B1/Kammer") skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> They=E2=80=99re only regenerated upon =E2=80=98make dist=E2=80=99 or =E2= =80=98make -C po/guix update-po=E2=80=99, >> I think. >> >> I just run =E2=80=98git reset --hard=E2=80=99 when that happens, which i= s rare. > > Actually I get the .po file changes when I build after e.g. "git reset > --hard && git clean -fdx", meaning essentially bring the directory to > the state of a freshly cloned repository. I haven't tried if it also > happens after "make clean", but it will certainly happen to those who > clone the repository and build for the first time. Yes, it happens on a first clone. Yet I=E2=80=99m uncomfortable with ignoring changes to these files because = we occasionally really want to update them and to see the changes. So I=E2=80=99m not sure what can be done. Ideas? Ludo=E2=80=99.