From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] gnulib: import sys_wait
Date: Tue, 7 Sep 2021 10:51:36 -0400 [thread overview]
Message-ID: <8b41bdc4-69ce-a54a-289d-f69c4d1c5daa@polymtl.ca> (raw)
In-Reply-To: <YTMjEEMr5cqpcxHa@vapier>
On 2021-09-04 3:41 a.m., Mike Frysinger wrote:
> On 03 Sep 2021 16:54, Simon Marchi wrote:
>> On 2021-06-13 1:25 a.m., Mike Frysinger via Gdb-patches wrote:
>>> A few sims use this to emulate process syscalls.
>>> gnulib/Makefile.in | 4 +
>>> gnulib/aclocal.m4 | 1 +
>>> gnulib/config.in | 3 +
>>> gnulib/configure | 99 +++++++++++++++++++++++
>>> gnulib/import/Makefile.am | 29 +++++++
>>> gnulib/import/Makefile.in | 35 +++++++--
>>> gnulib/import/m4/gnulib-cache.m4 | 2 +
>>> gnulib/import/m4/gnulib-comp.m4 | 5 ++
>>> gnulib/import/m4/sys_wait_h.m4 | 36 +++++++++
>>> gnulib/import/sys_wait.in.h | 131 +++++++++++++++++++++++++++++++
>>> gnulib/update-gnulib.sh | 1 +
>>> 11 files changed, 340 insertions(+), 6 deletions(-)
>>> create mode 100644 gnulib/import/m4/sys_wait_h.m4
>>> create mode 100644 gnulib/import/sys_wait.in.h
>>
>> I don't really know how to assess the risks of merging this, how things
>> could go wrong. But intuitively I think it should be relatively safe.
>> I'd say go ahead and merge it.
>
> i feel like this could be a review for every patch ;)
Haha, indeed, that would make life easier.
I meant that maybe somebody knows that we don't want to import a
particular module for some particular reason, a bit like what Eli said.
There might be some instances of this, but if so they should be
documented in gnulib/README, because there's no way to guess otherwise.
>
> we just branched gdb, so should be a good amount of time to let it bake
Agreed.
Simon
next prev parent reply other threads:[~2021-09-07 14:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 5:25 Mike Frysinger via Gdb-patches
2021-06-14 12:18 ` Eli Zaretskii via Gdb-patches
2021-06-14 14:35 ` Mike Frysinger via Gdb-patches
2021-06-14 14:43 ` Eli Zaretskii via Gdb-patches
2021-06-14 19:35 ` Mike Frysinger via Gdb-patches
2021-06-30 7:03 ` Mike Frysinger via Gdb-patches
2021-08-18 16:19 ` Mike Frysinger via Gdb-patches
2021-09-04 1:15 ` Mike Frysinger via Gdb-patches
2021-09-03 20:54 ` Simon Marchi via Gdb-patches
2021-09-04 7:41 ` Mike Frysinger via Gdb-patches
2021-09-07 14:51 ` Simon Marchi via Gdb-patches [this message]
2021-09-08 0:55 ` Mike Frysinger via Gdb-patches
2021-09-08 14:41 ` Simon Marchi via Gdb-patches
2021-09-08 20:20 ` 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=8b41bdc4-69ce-a54a-289d-f69c4d1c5daa@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