Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Beulich via Gdb-patches <gdb-patches@sourceware.org>
To: Nick Clifton <nickc@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>, Sam James <sam@gentoo.org>,
	Binutils <binutils@sourceware.org>,
	Nick Clifton via Gdb-patches <gdb-patches@sourceware.org>,
	Tzvetelin Katchov <katchov@gnu.org>
Subject: Re: RFC: Sort tarballs created by the src-release.sh script
Date: Tue, 4 Oct 2022 09:10:59 +0200	[thread overview]
Message-ID: <94778afd-a6ec-59b6-c8f9-c60aca991bc3@suse.com> (raw)
In-Reply-To: <1e772307-1f10-6e1c-5ffb-8513a41db5ab@redhat.com>

On 03.10.2022 16:40, Nick Clifton wrote:
> Hi Guys,
> 
>    [This appears to be getting slightly out of hand...]

It might seem like that, yes, but I guess that's not entirely unexpected
for a topic of that kind - different people have different expectations
and habits.

>> Not sure what "creation date" might mean here. Assuming the script is > (typically) run from a git tree, perhaps the commit date of the top> level commit on the branch would be best to use?
> Except that a commit to the branch that does not affect something that
> would go into the tarball would then result in a changed date.

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.

Jan

  parent reply	other threads:[~2022-10-04  7:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 12:59 Nick Clifton via Gdb-patches
2022-09-28 13:05 ` Andreas Schwab via Gdb-patches
2022-09-28 13:34   ` Nick Clifton via Gdb-patches
2022-09-29 12:24     ` Nick Clifton via Gdb-patches
2022-09-29 12:36       ` Jan Beulich via Gdb-patches
2022-09-30 11:38         ` Nick Clifton via Gdb-patches
2022-10-02  7:54           ` Sam James via Gdb-patches
2022-10-03  6:55             ` Jan Beulich via Gdb-patches
2022-10-03  6:59               ` Sam James via Gdb-patches
2022-10-03  7:41                 ` Andreas Schwab
2022-10-03 14:40               ` Nick Clifton via Gdb-patches
2022-10-03 19:56                 ` Andreas Schwab via Gdb-patches
2022-10-04  7:10                 ` Jan Beulich via Gdb-patches [this message]
2022-10-05 12:23                   ` Nick Clifton via Gdb-patches
2022-10-05 13:00                     ` Jan Beulich via Gdb-patches
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=94778afd-a6ec-59b6-c8f9-c60aca991bc3@suse.com \
    --to=gdb-patches@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    --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