From: fche@redhat.com (Frank Ch. Eigler)
To: Martin Jambor <mjambor@suse.cz>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Re: Checks that autotools generated files were re-generated correctly
Date: Tue, 07 Nov 2023 17:13:51 -0500 [thread overview]
Message-ID: <87o7g5gqjk.fsf@redhat.com> (raw)
In-Reply-To: <ri6il6e24pb.fsf@> (Martin Jambor's message of "Mon, 06 Nov 2023 18:04:48 +0100")
Martin Jambor <mjambor@suse.cz> writes:
> [...] I have inherited Martin Liška's buildbot script that checks
> that all sorts of autotools generated files, mainly configure scripts,
> were re-generated correctly when appropriate. [...]
The gccadmin account on sourceware already does some daily routine git
commits ("Daily bump."). You could decide to delegate regeneration of
the configury to the same service. It could run on a scheduled basis
rather than the commit hook, if people are angsty about that.
It would use designated master auto* tool versions. None of the
developers would have to struggle keeping them matched: just commit the
inputs. Or if they commit regenerated versions but with an oddball
auto* version, the sourceware bot could fix that later.
- FChE
next prev parent reply other threads:[~2023-11-07 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 17:04 Martin Jambor
2023-11-07 22:13 ` Frank Ch. Eigler [this message]
2023-11-08 23:30 ` Mark Wielaard
2023-11-15 19:48 ` Mark Wielaard
2023-11-16 18:37 ` Martin Jambor
[not found] <65491cda.c80a0220.5fa79.7688SMTPIN_ADDED_BROKEN@mx.google.com>
2023-11-06 17:19 ` Christophe Lyon
2023-11-07 7:38 ` Maxim Kuvyrkov
2023-11-07 13:50 ` Carlos O'Donell
2023-11-07 14:36 ` Martin Jambor
[not found] ` <654a4b60.2e0a0220.7f3b.6e5aSMTPIN_ADDED_BROKEN@mx.google.com>
2023-11-07 15:42 ` Christophe Lyon
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=87o7g5gqjk.fsf@redhat.com \
--to=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=mjambor@suse.cz \
/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).