all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27593-done@debbugs.gnu.org
Subject: bug#27593: [PATCH] gnu: groff: Make build reproducible.
Date: Sun, 10 Sep 2017 15:13:12 +0200	[thread overview]
Message-ID: <87tw0a7l3r.fsf@gnu.org> (raw)
In-Reply-To: <20170909231742.5819bb31@scratchpost.org> (Danny Milosavljevic's message of "Sat, 9 Sep 2017 23:17:42 +0200")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Hi Ludo,
>
> On Sat, 09 Sep 2017 22:31:36 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Maybe now is the time to push this to ‘core-updates’?
>> 
>> (I was just hit by this reproducibility issue for a PDF file made with
>> groff…)
>
> Isn't it pushed already?

Oh it is, but in the new ‘core-updates’ (I was looking at ‘master’.).

Perfect, happily closing the bug now.  :-)

Thanks,
Ludo’.

      reply	other threads:[~2017-09-10 13:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06  0:54 bug#27593: groff build is not reproducible Danny Milosavljevic
2017-07-06  1:01 ` bug#27593: [PATCH] gnu: groff: Remove timestamps Danny Milosavljevic
2017-07-06  1:47 ` bug#27593: [PATCH v2] " Danny Milosavljevic
2017-07-09 13:00   ` Marius Bakke
2017-07-09 19:51     ` Ludovic Courtès
2017-07-09 21:27       ` bug#27593: [PATCH v3] " Danny Milosavljevic
2017-07-09 21:55         ` Marius Bakke
2017-07-10  9:05           ` Ludovic Courtès
2017-07-10 10:40             ` Danny Milosavljevic
2017-07-10 16:37 ` bug#27593: [PATCH] gnu: groff: Make build reproducible Danny Milosavljevic
2017-07-10 19:07   ` Marius Bakke
2017-07-10 19:28     ` Danny Milosavljevic
2017-07-11  9:31   ` Ludovic Courtès
2017-09-09 20:31     ` Ludovic Courtès
2017-09-09 21:17       ` Danny Milosavljevic
2017-09-10 13:13         ` Ludovic Courtès [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=87tw0a7l3r.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27593-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.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.