Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ppluzhnikov@google.com, gdb-patches@sourceware.org
Subject: Re: [DOCO/PING] Re: [patch] Replace deprecated_memory_changed_hook  with an observer.
Date: Wed, 02 Dec 2009 18:19:00 -0000	[thread overview]
Message-ID: <20091202181908.GD4020@adacore.com> (raw)
In-Reply-To: <83ljhll0m4.fsf@gnu.org>

> Sorry.  I generally don't think I need to approve changes to
> observer.texi, because it's not docs.  It's code disguised as docs.

Understood. observer.texi is included by gdbint, so the contents
does go in a document, but I'm happy either way. Like I said, this
is not the most difficult part of the documentation to fix if there
is any issue.

-- 
Joel


  reply	other threads:[~2009-12-02 18:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 19:42 Paul Pluzhnikov
2009-11-25 20:48 ` Joel Brobecker
2009-11-25 21:14   ` Paul Pluzhnikov
2009-12-02 17:38     ` [DOCO/PING] " Joel Brobecker
2009-12-02 18:00       ` Eli Zaretskii
2009-12-02 18:19         ` Joel Brobecker [this message]
2009-12-02 19:30         ` Paul Pluzhnikov

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=20091202181908.GD4020@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.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