From: Andreas Schwab <schwab@linux-m68k.org>
To: Sam James via Gdb-patches <gdb-patches@sourceware.org>
Cc: Jan Beulich <jbeulich@suse.com>, Sam James <sam@gentoo.org>,
Tzvetelin Katchov <katchov@gnu.org>,
Nick Clifton <nickc@redhat.com>,
Binutils <binutils@sourceware.org>
Subject: Re: RFC: Sort tarballs created by the src-release.sh script
Date: Mon, 03 Oct 2022 09:41:12 +0200 [thread overview]
Message-ID: <87tu4lnylj.fsf@linux-m68k.org> (raw)
In-Reply-To: <38F08F3E-EFA6-4ABA-9CEE-60306E872C25@gentoo.org> (Sam James via Gdb-patches's message of "Mon, 3 Oct 2022 07:59:04 +0100")
On Okt 03 2022, Sam James via Gdb-patches wrote:
> I meant whatever date folks consider to have been the creation of the Binutils project. First commit, announcement, first release, whatever.
I think using the date of the commit from which the tarball is being
created makes the most sense (this is what git archive does).
Another thing to consider is the recorded permission of the files.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-10-03 7:41 UTC|newest]
Thread overview: 16+ 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-03 6:55 ` Jan Beulich
2022-10-03 6:59 ` Sam James
2022-10-03 7:41 ` Andreas Schwab [this message]
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
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=87tu4lnylj.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jbeulich@suse.com \
--cc=katchov@gnu.org \
--cc=nickc@redhat.com \
--cc=sam@gentoo.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.
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).