unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Julien Lepiller" <julien@lepiller.eu>,
	26247@debbugs.gnu.org
Subject: bug#26247: Gettext introduces timestamps in .mo files
Date: Sat, 08 Oct 2022 16:25:21 +0200	[thread overview]
Message-ID: <868rlqtmsu.fsf@gmail.com> (raw)
In-Reply-To: <875z58fp8e.fsf@gmail.com> ("Miguel Ángel Arruga Vivas"'s message of "Fri, 11 Dec 2020 14:26:25 +0100")

Hi Miguel,

It is about an old patch [2] and on old message from Dec. 2020.

On Fri, 11 Dec 2020 at 14:26, Miguel Ángel Arruga Vivas <rosen644835@gmail.com> wrote:

> This bug has already been reported upstream[1] and probably I'll push it
> as soon as I have more test cases prepared and receive a brief review,
> but I can prepare a patch for previous versions if it's needed too.
>
> Best regards,
> Miguel
>
> [1] https://savannah.gnu.org/bugs/?59658

Are commits 4343ca8ba5b02c8fe09e5bd681abbc0440ab8b08 and following the
ones mentioned here?

Well, I am not sure to understand if it had been fixed upstream [1].


Cheers,
simon

2: <http://issues.guix.gnu.org/issue/26247>




  parent reply	other threads:[~2022-10-08 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 22:54 bug#26247: Gettext introduces timestamps in .mo files Ludovic Courtès
2020-12-01 18:46 ` zimoun
2020-12-03 10:32   ` Ludovic Courtès
2020-12-03 12:07     ` Julien Lepiller
2020-12-03 14:41       ` Ludovic Courtès
2020-12-11 13:26         ` Miguel Ángel Arruga Vivas
2020-12-14  9:09           ` Ludovic Courtès
2022-10-08 14:25           ` zimoun [this message]
2023-10-16 23:48             ` Simon Tournier
2023-10-17 10:11               ` Julien Lepiller

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=868rlqtmsu.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=26247@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.org \
    --cc=rosen644835@gmail.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).