Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/doc] There's always a thread
Date: Thu, 10 Dec 2015 16:37:00 -0000	[thread overview]
Message-ID: <83twnq9s4d.fsf@gnu.org> (raw)
In-Reply-To: <1449756899-18063-1-git-send-email-palves@redhat.com>

> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 10 Dec 2015 14:14:59 +0000
> 
> This warning is a few years out of date -- there's always a thread
> nowadays.
> 
> gdb/doc/ChangeLog:
> 
> 	* gdb.texinfo (Threads): Replace warning with explanation/example
> 	about single-threaded programs.

This is OK, but your particular wording makes it sound like systems
that have no threading libraries at all are not covered by the
description.  How about not mentioning the threading library and the
rest of confusing details, and instead just talk about single-threaded
programs?

Thanks.


  reply	other threads:[~2015-12-10 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 14:15 Pedro Alves
2015-12-10 16:37 ` Eli Zaretskii [this message]
2015-12-10 17:10   ` Pedro Alves
2015-12-10 17:38     ` Eli Zaretskii
2015-12-10 17:49       ` Pedro Alves

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=83twnq9s4d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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