Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Delete gdb-mi.el
Date: Fri, 25 Sep 2009 02:00:00 -0000	[thread overview]
Message-ID: <19132.9286.605333.176763@totara.tehura.co.nz> (raw)
In-Reply-To: <20090925014041.GH2112@adacore.com>

 > > I think we should also remove it from the 7.0 branch.
 > 
 > Whatever is good for you is good for me, but I would have thought
 > that you would have prefered to wait until the next emacs release...
 > Unless the "next emacs release" already happened?  In any case,
 > I think it's fair to let you do what you think is best; I think
 > you're the only one really maintaining that file.

Ok, I've just removed it from the trunk.  I don't think anybody is interested
in this file but it can't do any harm in 7.0.

Thanks,
Nick


  reply	other threads:[~2009-09-25  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 23:13 Nick Roberts
2009-09-25  1:40 ` Joel Brobecker
2009-09-25  2:00   ` Nick Roberts [this message]
2009-09-25  8:49 ` Eli Zaretskii
2009-09-25 11:02   ` Nick Roberts

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=19132.9286.605333.176763@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.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