From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: common: modernize gennltvals.sh
Date: Mon, 18 Jan 2021 16:27:05 -0500 [thread overview]
Message-ID: <68cfceea-7183-e21d-0482-4838fc882861@polymtl.ca> (raw)
In-Reply-To: <YAX6gNK+djvFwGsg@vapier>
On 2021-01-18 4:15 p.m., Mike Frysinger wrote:
> in what context ? i assume it's off-limits for people downloading a
> release and building e.g. gdb or gas. but is it acceptable for devs
> doing dev work (which is what this thing is) ?
For development, I would be very comfortable requiring bash or python3,
there's a limit to how much we have to live in the past. bash and
python3 are ubiquitous enough.
For building releases, I would personally be fine with it, but I
expect others to disagree.
Simon
next prev parent reply other threads:[~2021-01-18 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 10:10 Mike Frysinger via Gdb-patches
2021-01-17 10:36 ` [PATCH] sim: common: delete configure & Makefile Mike Frysinger via Gdb-patches
2021-01-18 10:01 ` Andrew Burgess
2021-01-18 10:00 ` [PATCH] sim: common: modernize gennltvals.sh Andrew Burgess
2021-01-18 17:09 ` Mike Frysinger via Gdb-patches
2021-01-18 14:04 ` Simon Marchi via Gdb-patches
2021-01-18 17:13 ` Mike Frysinger via Gdb-patches
2021-01-18 17:19 ` Simon Marchi via Gdb-patches
2021-01-18 17:52 ` Mike Frysinger via Gdb-patches
2021-01-18 18:08 ` Simon Marchi via Gdb-patches
2021-01-18 21:15 ` Mike Frysinger via Gdb-patches
2021-01-18 21:27 ` Simon Marchi via Gdb-patches [this message]
2021-01-20 19:51 ` Tom Tromey
2021-01-18 17:20 ` [PATCH v2] " Mike Frysinger via Gdb-patches
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=68cfceea-7183-e21d-0482-4838fc882861@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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