From: "Ludovic Courtès" <ludo@gnu.org>
To: 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:08:54 +0100 [thread overview]
Message-ID: <87bm5gsjqh.fsf@gnu.org> (raw)
In-Reply-To: <87mup37vgq.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Mon, 17 Dec 2018 15:24:21 -0500")
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’.
next prev parent reply other threads:[~2018-12-20 8:09 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 [this message]
2018-12-20 8:45 ` zimoun
2018-12-20 9:33 ` Julien Lepiller
2018-12-20 8:48 ` Julien Lepiller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bm5gsjqh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@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 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.