Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matt Rice <ratmice@gmail.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org,
	pierre.muller@ics-cnrs.unistra.fr
Subject: Re: [RFC] Missing sleep function for mingw hosts
Date: Wed, 30 Mar 2011 04:12:00 -0000	[thread overview]
Message-ID: <83y63xr3b0.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimdp28yv_Q+tsDWOqFsNWaifZfRUB7K629tUuha@mail.gmail.com>

> Date: Tue, 29 Mar 2011 13:21:55 -0700
> From: Matt Rice <ratmice@gmail.com>
> Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org, 
> 	pierre.muller@ics-cnrs.unistra.fr
> 
> fwiw, looking at the output of:
> 
> https://gitorious.org/gnulib-module-graph/gnulib-module-graph
> 
> importing sleep brings in 2 dependencies which we do not already have,
> unistd, and verify (in addition to the sleep module).

Aha, and all that for a function whose definition, including empty
lines and comments, is 14 lines (10 lines without that slack).
Typical.


  reply	other threads:[~2011-03-29 22:05 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       ` [RFC] Missing sleep function for mingw hosts Eli Zaretskii
2011-03-30  0:06         ` Matt Rice
2011-03-30  4:12           ` Eli Zaretskii [this message]
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=83y63xr3b0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    --cc=ratmice@gmail.com \
    /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