From: Nick Roberts <nickrob@snap.net.nz>
To: msnyder@sonic.net
Cc: "Bob Rossi" <bob_rossi@cox.net>,
"Daniel Jacobowitz" <drow@false.org>,
gdb-patches@sourceware.org
Subject: Re: ping Re: [PATCH] dead code in mi-interp
Date: Tue, 14 Aug 2007 11:27:00 -0000 [thread overview]
Message-ID: <18113.37112.950132.140921@farnswood.snap.net.nz> (raw)
In-Reply-To: <14206.12.7.175.2.1187045207.squirrel@webmail.sonic.net>
> So it seems like three people favor removing it, and one person opposes.
>
> Can we reach a resolution?
I don't feel that strongly about it and, in any case, the MAINTAINERS file says
that you have the authority to make the change. Go for it.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-08-14 11:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 22:25 msnyder
2007-08-08 23:24 ` Nick Roberts
2007-08-09 14:47 ` Jim Blandy
2007-08-09 14:57 ` Daniel Jacobowitz
2007-08-09 21:12 ` Nick Roberts
2007-08-09 21:29 ` msnyder
2007-08-09 22:11 ` Bob Rossi
2007-08-10 4:00 ` Nick Roberts
2007-08-10 11:22 ` Bob Rossi
2007-08-10 21:49 ` msnyder
2007-08-13 22:47 ` ping " msnyder
2007-08-14 11:27 ` Nick Roberts [this message]
2007-08-14 19:51 ` msnyder
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=18113.37112.950132.140921@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob_rossi@cox.net \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
/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