From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, pierre.muller@ics-cnrs.unistra.fr
Subject: Re: [RFC] Missing sleep function for mingw hosts
Date: Tue, 29 Mar 2011 22:05:00 -0000 [thread overview]
Message-ID: <831v1psnl9.fsf@gnu.org> (raw)
In-Reply-To: <201103291523.46954.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Tue, 29 Mar 2011 15:23:46 +0100
> Cc: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>,
> "'Eli Zaretskii'" <eliz@gnu.org>
>
> > > I'd rather we had a replacement in win32-nat.c, instead of importing
> > > gobs of gnulib stuff needed to provide such a trivial replacement.
> > > gnulib is GPL, so we can simply copy the code into our sources.
>
> gnulib has a mechanism (which we are already using) where
> we just import the modules we need. We don't import the whole
> thing.
I know, but "just the modules we need" are typically huge relative to
small problems they solve, this one in particular.
Anyway, I'm glad that a much more elegant solution is already
available in GDB, in the form of gdb_usleep.
next prev parent reply other threads:[~2011-03-29 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 8:11 Pierre Muller
2011-03-29 13:10 ` Eli Zaretskii
2011-03-29 14:23 ` Pierre Muller
2011-03-29 15:40 ` Pedro Alves
2011-03-29 15:41 ` Kai Tietz
2011-03-29 15:43 ` [RFA] use gdb_usleep instead of sleep in remote-mips.c (was Missing sleep function for mingw hosts) Pierre Muller
2011-03-29 15:53 ` Joel Brobecker
2011-03-29 16:54 ` Pierre Muller
2011-03-29 22:05 ` Eli Zaretskii [this message]
2011-03-30 0:06 ` [RFC] Missing sleep function for mingw hosts Matt Rice
2011-03-30 4:12 ` Eli Zaretskii
2011-03-30 6:25 ` Matt Rice
2011-03-30 9:25 ` Eli Zaretskii
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=831v1psnl9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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