unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix <guix-devel@gnu.org>, Feng Shu <tumashu@163.com>
Subject: Re: Should these files ignored?
Date: Wed, 27 May 2015 17:04:08 +0200	[thread overview]
Message-ID: <87zj4qhxjr.fsf@gnu.org> (raw)
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")

taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> They’re only regenerated upon ‘make dist’ or ‘make -C po/guix update-po’,
>> I think.
>>
>> I just run ‘git reset --hard’ when that happens, which is 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’m uncomfortable with ignoring changes to these files because we
occasionally really want to update them and to see the changes.

So I’m not sure what can be done.  Ideas?

Ludo’.

  reply	other threads:[~2015-05-27 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  8:45 Should these files ignored? Feng Shu
2015-05-25 20:57 ` Ludovic Courtès
2015-05-26 15:45   ` Pjotr Prins
2015-05-26 20:45     ` Ludovic Courtès
2015-05-26 21:37       ` Taylan Ulrich Bayırlı/Kammer
2015-05-27 15:04         ` Ludovic Courtès [this message]
2015-05-27 16:40           ` Pjotr Prins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zj4qhxjr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=taylanbayirli@gmail.com \
    --cc=tumashu@163.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).