From: Simon Marchi <simark@simark.ca>
To: Christophe Lyon <christophe.lyon@linaro.org>, buildbot@sourceware.org
Subject: Re: [PATCH 5/5] autoregen.py: Add introduction comment
Date: Wed, 17 Apr 2024 11:12:51 -0400 [thread overview]
Message-ID: <36e0b0c0-2e14-44ec-905c-00de568ae930@simark.ca> (raw)
In-Reply-To: <20240417145033.2077525-5-christophe.lyon@linaro.org>
On 2024-04-17 10:50, Christophe Lyon wrote:
> To give more context to users, with the plan of moving this file to
> contrib/ in binutils-gdb and gcc repositories.
> ---
> builder/containers/autoregen.py | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/builder/containers/autoregen.py b/builder/containers/autoregen.py
> index 277dcb7..c392bf8 100755
> --- a/builder/containers/autoregen.py
> +++ b/builder/containers/autoregen.py
> @@ -1,5 +1,12 @@
> #!/usr/bin/env python3
>
> +# This script helps to regenerate files managed by autotools and
> +# autogen in binutils-gdb and gcc repositories.
> +
> +# In can be used by buildbots to check that the current repository
In -> It
Otherwise, the series LGTM.
Simon
next prev parent reply other threads:[~2024-04-17 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 14:50 [PATCH 1/5] autoregen.py: enable autoreconf for gcc, libdecnumber, libiberty, libobjc Christophe Lyon
2024-04-17 14:50 ` [PATCH 2/5] autoregen.py: Move subdirs common to binutils-gdb and gcc Christophe Lyon
2024-04-17 14:50 ` [PATCH 3/5] autoregen.py: improve comment Christophe Lyon
2024-04-17 14:50 ` [PATCH 4/5] autoregen.py: libcpp can use autoreconf Christophe Lyon
2024-04-18 21:46 ` Mark Wielaard
2024-04-19 8:20 ` Christophe Lyon
2024-04-17 14:50 ` [PATCH 5/5] autoregen.py: Add introduction comment Christophe Lyon
2024-04-17 15:12 ` Simon Marchi [this message]
2024-04-18 9:59 ` Christophe Lyon
2024-04-18 21:55 ` Mark Wielaard
2024-04-19 8:22 ` Christophe Lyon
2024-04-18 21:53 ` [PATCH 1/5] autoregen.py: enable autoreconf for gcc, libdecnumber, libiberty, libobjc Mark Wielaard
2024-04-19 8:21 ` 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=36e0b0c0-2e14-44ec-905c-00de568ae930@simark.ca \
--to=simark@simark.ca \
--cc=buildbot@sourceware.org \
--cc=christophe.lyon@linaro.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).