Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: cgd@google.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Try2: Inform about new thread in a single place.
Date: Mon, 07 Jan 2008 21:02:00 -0000	[thread overview]
Message-ID: <uejcttkmd.fsf@gnu.org> (raw)
In-Reply-To: <200801071833.51795.vladimir@codesourcery.com> (message from 	Vladimir Prus on Mon, 7 Jan 2008 18:33:51 +0300)

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Mon, 7 Jan 2008 18:33:51 +0300
> Cc: cgd@google.com,
>  gdb-patches@sources.redhat.com
> 
> On Saturday 22 December 2007 12:59:29 Eli Zaretskii wrote:
> > > From: Vladimir Prus <vladimir@codesourcery.com>
> > > Date: Fri, 21 Dec 2007 22:15:43 +0300
> > > Cc: gdb-patches@sources.redhat.com
> > > 
> > > > * [eliz] thread-attach -> thread-events in the gdb.texinfo change. *
> > > > (I forgot to change one copy of my old command name)
> > > > 
> > > > * [eliz] GDB -> @value(GDBN} in the gdb.texinfo change as well.
> > > 
> > > I've missed those, sorry. Here's the revised patch.
> > 
> > Thanks, but one instance of a literal "GDB" was still left uncaught:
> > 
> > > +Show whether messages will be printed when GDB detects that threads
> 
> Is the patch OK to commit, as soon as this bit is fixed?

Yes, as far as I'm concerned.


  reply	other threads:[~2008-01-07 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 18:51 Vladimir Prus
2007-12-21 19:03 ` Chris Demetriou
2007-12-22  5:22   ` Vladimir Prus
2007-12-22 10:20     ` Eli Zaretskii
2008-01-07 15:34       ` Vladimir Prus
2008-01-07 21:02         ` Eli Zaretskii [this message]
2008-01-07 21:09           ` Daniel Jacobowitz
2008-01-23 11:28             ` Vladimir Prus

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=uejcttkmd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cgd@google.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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