From: Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Bruno Haible <bruno@clisp.org>,
bug-gnulib@gnu.org
Subject: Re: RFC: git-commit based mtime-reproducible tarballs
Date: Tue, 17 Jan 2023 00:00:40 +0100 [thread overview]
Message-ID: <87tu0qnkyv.fsf@josefsson.org> (raw)
In-Reply-To: <63f570523b5bd4663fae92edd6da921f01eee73d.camel@planete-kraus.eu> (Vivien Kraus's message of "Mon, 16 Jan 2023 10:45:05 +0100")
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Vivien Kraus <vivien@planete-kraus.eu> writes:
> 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.
Indeed, good point. I think 'make dist' should continue to work in
shallow clones, with its obvious consequences (incomplete ChangeLog,
non-deterministic mtime of version controlled files, anything else?).
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2023-01-16 23:01 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
2023-01-16 11:48 ` Bruno Haible
2023-01-16 23:00 ` Simon Josefsson via Gnulib discussion list [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87tu0qnkyv.fsf@josefsson.org \
--to=bug-gnulib@gnu.org \
--cc=bruno@clisp.org \
--cc=eggert@cs.ucla.edu \
--cc=simon@josefsson.org \
--cc=vivien@planete-kraus.eu \
/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.
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).