From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>,
Binutils <binutils@sourceware.org>,
Nick Clifton via Gdb-patches <gdb-patches@sourceware.org>,
Tzvetelin Katchov <katchov@gnu.org>, Sam James <sam@gentoo.org>
Subject: Re: RFC: Sort tarballs created by the src-release.sh script
Date: Wed, 5 Oct 2022 15:00:40 +0200 [thread overview]
Message-ID: <78bb30f3-f747-a2f5-a0cd-839434bcdfa5@suse.com> (raw)
In-Reply-To: <c512c0f6-5c3b-294c-69e5-5377518a93ce@redhat.com>
On 05.10.2022 14:23, Nick Clifton wrote:
> Hi Guys,
>
> On 10/4/22 08:10, Jan Beulich wrote:
>> Every commit should be considered to affect the tarball, imo, as such
>> effects could also be indirect. If you really wanted to go that route,
>> then perhaps an alternative would be to use the commit date of the
>> most recent commit touching bfd/version.m4.
>
> Hmm, except that would probably only be appropriate for binutils tarballs,
> not others.
>
> So how about the attached patch ? This one adds a new command line option to
> src-release.sh. If it is not used then the behaviour is not changed in any
> way. If the new option is used, it provides a date that is passed to tar's
> --mtime option, along with triggering the use of sort and the other tar
> options necessary to make a reproducible tarball. So:
>
> src-release.sh -x -r `git log -1 --format=%cd --date=format:%F bfd/version.m4` binutils
>
> should create a pretty consistent tarball.
Lgtm, fwiw. Just one nit: You may want to add the missing 'b' for
"tarball" in the new help text line.
Jan
next prev parent reply other threads:[~2022-10-05 13:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 12:59 Nick Clifton
2022-09-28 13:05 ` Andreas Schwab
2022-09-28 13:34 ` Nick Clifton
2022-09-29 12:24 ` Nick Clifton
2022-09-29 12:36 ` Jan Beulich
2022-09-30 11:38 ` Nick Clifton
2022-10-02 7:54 ` Sam James
2022-10-02 7:54 ` Sam James
2022-10-03 6:55 ` Jan Beulich
2022-10-03 6:59 ` Sam James
2022-10-03 7:41 ` Andreas Schwab
2022-10-03 14:40 ` Nick Clifton
2022-10-03 19:56 ` Andreas Schwab
2022-10-04 7:10 ` Jan Beulich
2022-10-05 12:23 ` Nick Clifton
2022-10-05 13:00 ` Jan Beulich [this message]
2022-10-03 7:47 ` Andreas Schwab
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=78bb30f3-f747-a2f5-a0cd-839434bcdfa5@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=katchov@gnu.org \
--cc=nickc@redhat.com \
--cc=sam@gentoo.org \
--cc=schwab@suse.de \
/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).