unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Christopher Lemmer Webber" <cwebber@dustycloud.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: What's up with the .texi files always "changing"?
Date: Thu, 20 Dec 2018 09:48:22 +0100	[thread overview]
Message-ID: <B53ECBD0-1238-4B80-927A-582D9D476CA4@lepiller.eu> (raw)
In-Reply-To: <87bm5gsjqh.fsf@gnu.org>

Just add them to .gitignore would hide the issue. As long as we don't forget to commit the texi files along with uodates to the po files, it's fine.

Another solution would be to find a way to be able to generate them completely, so we don't need to add them to git. The issue is that the autotools don't like that: they refuse to work if the texi files are not present, which would be the case for fresh checkouts. I'd prefer this kind of solution though.

Note that .po files are also updated after a fresh make on a clean checkout, but maybe less often than the translated manuals.

Le 20 décembre 2018 09:08:54 GMT+01:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hello,
>
>Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
>
>> Changes not staged for commit:
>>   (use "git add <file>..." to update what will be committed)
>>   (use "git checkout -- <file>..." to discard changes in working
>directory)
>>
>> 	modified:   doc/contributing.de.texi
>> 	modified:   doc/contributing.fr.texi
>> 	modified:   doc/guix.de.texi
>> 	modified:   doc/guix.fr.texi
>>
>> Why does this keep happening?  If these are autogenerated, why are
>they
>> committed into git?  If they aren't autogenerated, why are they
>changing?
>
>They are automatically updated, but not actually “generated”: fellow
>hackers like Julien worked hard to write these translations.  :-)
>
>However it seems that updates are triggered too often, presumably since
>commit 7565d40e1e583b35148088bcf79760b9f95f91d9.
>
>Julien, any idea how we could improve on this?
>
>Thanks,
>Ludo’.

  parent reply	other threads:[~2018-12-20  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 20:24 What's up with the .texi files always "changing"? Christopher Lemmer Webber
2018-12-20  8:08 ` Ludovic Courtès
2018-12-20  8:45   ` zimoun
2018-12-20  9:33     ` Julien Lepiller
2018-12-20  8:48   ` Julien Lepiller [this message]
2018-12-21 21:09     ` Ludovic Courtès

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=B53ECBD0-1238-4B80-927A-582D9D476CA4@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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).