Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: add more hacking notes
Date: Mon, 12 Apr 2010 18:26:00 -0000	[thread overview]
Message-ID: <83r5mky1bf.fsf@gnu.org> (raw)
In-Reply-To: <201004121411.57943.vapier@gentoo.org>

> From: Mike Frysinger <vapier@gentoo.org>
> Date: Mon, 12 Apr 2010 14:11:56 -0400
> Cc: Joel Brobecker <brobecker@adacore.com>,  gdb-patches@sourceware.org
> 
> > This isn't user-visible docs, so all I did was proofread it
> 
> so once i fixed these, i may commit ?

As far as I'm concerned, yes.  Not sure who else, if anyone, needs to
approve these patches.


  reply	other threads:[~2010-04-12 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10 18:58 Mike Frysinger
2010-04-12 14:56 ` Joel Brobecker
2010-04-12 17:36   ` Eli Zaretskii
2010-04-12 18:12     ` Mike Frysinger
2010-04-12 18:26       ` Eli Zaretskii [this message]
2010-04-12 19:57         ` Joel Brobecker

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=83r5mky1bf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.org \
    /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