bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Vivien Kraus <vivien@planete-kraus.eu>
To: Paul Eggert <eggert@cs.ucla.edu>, Bruno Haible <bruno@clisp.org>
Cc: Simon Josefsson <simon@josefsson.org>, bug-gnulib@gnu.org
Subject: Re: RFC: git-commit based mtime-reproducible tarballs
Date: Mon, 16 Jan 2023 10:45:05 +0100	[thread overview]
Message-ID: <63f570523b5bd4663fae92edd6da921f01eee73d.camel@planete-kraus.eu> (raw)
In-Reply-To: <ba9aaa86-ccc2-1912-9cea-42b99a88b6da@cs.ucla.edu>


Le dimanche 15 janvier 2023 à 08:03 -0800, Paul Eggert a écrit :
> For TZDB, where users have long wanted reproducibility, I use
> something 
> like this in a Makefile recipe for each source file $$file:
>               time=`git log -1 --format='tformat:%ct' $$file` &&
>               touch -cmd @$$time $$file

If your texinfo file includes version.texi, then its modification date
is very important because it impacts the date that appears in the final
file. Your solution is in my opinion the only correct way to answer the

However, there are situations in which you only have access to a
shallow clone of the git repository (for instance, Gitlab CI). I am not
sure how this solution would work in that case.

Best regards,


  parent reply	other threads:[~2023-01-16  9:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87h6wtgmhy.fsf__22556.7857896507$1673713908$gmane$org@redhat.com>
2023-01-15 11:01 ` RFC: git-commit based mtime-reproducible tarballs Simon Josefsson via Gnulib discussion list
2023-01-15 13:21   ` Bruno Haible
2023-01-15 16:03     ` Paul Eggert
2023-01-15 22:25       ` Bruno Haible
2023-01-16  8:40         ` Simon Josefsson via Gnulib discussion list
2023-01-16  8:51           ` Jim Meyering
2023-01-16  9:45       ` Vivien Kraus [this message]
2023-01-16 11:48         ` Bruno Haible
2023-01-16 23:00         ` Simon Josefsson via Gnulib discussion list
2023-01-16  8:28     ` Simon Josefsson via Gnulib discussion list

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:

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=63f570523b5bd4663fae92edd6da921f01eee73d.camel@planete-kraus.eu \
    --to=vivien@planete-kraus.eu \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=simon@josefsson.org \


* 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.
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).