From: Mike Frysinger <vapier@gentoo.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gnulib: import sys_wait
Date: Wed, 8 Sep 2021 16:20:07 -0400 [thread overview]
Message-ID: <YTka99bQ/SHvsyWZ@vapier> (raw)
In-Reply-To: <314db7e4-1e03-384f-e717-8d1d99744424@polymtl.ca>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On 08 Sep 2021 10:41, Simon Marchi via Gdb-patches wrote:
> > there's no existing notes like that in gnulib/README that i can see. how
> > about updating gnulib/update-gnulib.sh to list dependencies for each module
> > that is listed there ? that'd solve the issue of the two files falling out
> > of sync.
>
> I don't follow you. I was just saying that sometimes, there are reasons
> why we don't want to import a given gnulib module, because it doesn't
> work for us. Like, there was an issue with stat, I don't remember the
> details exactly. If that happens, it would be good to have a note
> somewhere explaining it.
sorry, i thought you wanted to document modules that were imported, not ones
that we were explicitly omitting. i'm not familiar with the history of the
stat module here to help.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-09-08 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 5:25 Mike Frysinger
2021-06-14 12:18 ` Eli Zaretskii
2021-06-14 14:35 ` Mike Frysinger
2021-06-14 14:43 ` Eli Zaretskii
2021-06-14 19:35 ` Mike Frysinger
2021-06-30 7:03 ` Mike Frysinger
2021-08-18 16:19 ` Mike Frysinger
2021-09-04 1:15 ` Mike Frysinger
2021-09-03 20:54 ` Simon Marchi
2021-09-04 7:41 ` Mike Frysinger
2021-09-07 14:51 ` Simon Marchi
2021-09-08 0:55 ` Mike Frysinger
2021-09-08 14:41 ` Simon Marchi
2021-09-08 20:20 ` Mike Frysinger [this message]
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=YTka99bQ/SHvsyWZ@vapier \
--to=vapier@gentoo.org \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).