all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix <guix-devel@gnu.org>, Feng Shu <tumashu@163.com>
Subject: Re: Should these files ignored?
Date: Wed, 27 May 2015 18:40:43 +0200	[thread overview]
Message-ID: <20150527164043.GC31828@thebird.nl> (raw)
In-Reply-To: <87zj4qhxjr.fsf@gnu.org>

Make it a separate make target.

Pj.

On Wed, May 27, 2015 at 05:04:08PM +0200, Ludovic Courtès wrote:
> 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 16:41 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
2015-05-27 16:40           ` Pjotr Prins [this message]

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

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

  git send-email \
    --in-reply-to=20150527164043.GC31828@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.