From: "Martin Liška" <mliska@suse.cz>
To: Jason Merrill <jason@redhat.com>,
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Harald Anlauf <anlauf@gmx.de>, gfortran <fortran@gcc.gnu.org>,
gcc-patches List <gcc-patches@gcc.gnu.org>,
Bernhard Reutner-Fischer <aldot@gcc.gnu.org>,
Carlos O'Donell <codonell@redhat.com>
Subject: Re: git out-of-order commit (was Re: [PATCH] Fortran: Remove unused declaration)
Date: Mon, 23 Jan 2023 11:37:22 +0100 [thread overview]
Message-ID: <0f44907d-d48c-4800-ba26-62d7f4bbd841@suse.cz> (raw)
In-Reply-To: <CADzB+2m85cU-Q12-81zr5vHZpSF1fhhGqKs7oB2rLLzTeRiWQg@mail.gmail.com>
On 1/20/23 18:33, Jason Merrill wrote:
> Martin, I wonder about having the hooks reject out-of-order CommitDate
> in future?
Yes, I would do that. Looking at the last 30K commmits I see just a few violations
of the order:
UNIXTS hash
1668298622 30d77d49628
1630019619 5889e842ae4
1626967834 3f7a2374d31
1624564915 a0accaa9984
1620660174 0498d2d09a2
1606210175 f72175357d0
1605630503 8895913273b
1604409789 1528f34341b
1601415121 f836f3bc8f7
1593773652 9bc2c2347d5
1588873342 b9250b3cb91
1582563261 9069e9484ce
Martin
next prev parent reply other threads:[~2023-01-23 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 21:05 [PATCH] Fortran: Remove unused declaration Bernhard Reutner-Fischer
2022-11-12 21:23 ` Harald Anlauf
2023-01-19 19:39 ` git out-of-order commit (was Re: [PATCH] Fortran: Remove unused declaration) Jason Merrill
2023-01-19 20:20 ` Harald Anlauf
2023-01-20 4:26 ` Bernhard Reutner-Fischer
2023-01-20 17:33 ` Jason Merrill
2023-01-23 10:37 ` Martin Liška [this message]
2023-01-20 22:01 ` Carlos O'Donell
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=0f44907d-d48c-4800-ba26-62d7f4bbd841@suse.cz \
--to=mliska@suse.cz \
--cc=aldot@gcc.gnu.org \
--cc=anlauf@gmx.de \
--cc=codonell@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=rep.dot.nop@gmail.com \
/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).