Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -data-list-changed-registers (Take 2)
Date: Fri, 17 Jun 2005 03:13:00 -0000	[thread overview]
Message-ID: <17074.16470.814479.200726@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050617015059.GC17013@nevyn.them.org>

 > The only reason I haven't approved the gdb-mi.el you last posted was
 > because it depended on the MI patch which you just reminded me to look
 > at (which was an interface change, and I hadn't had a chance to
 > digest it yet).  I do not want you to commit anything which uses MI
 > interfaces that don't exist yet!  Normally, I'd be perfectly willing to
 > rubber-stamp it in.

I'm thinking more generally.  In Emacs, I commit about one change a week.  If
I need approval, then I will group changes together and do it less often, but
someone is always available to approve those changes then there is no problem.

Nick


  reply	other threads:[~2005-06-17  3:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 11:12 [PATCH] -data-list-changed-registers Nick Roberts
2005-06-03 19:13 ` Daniel Jacobowitz
2005-06-03 22:35   ` Nick Roberts
2005-06-03 22:36     ` Daniel Jacobowitz
2005-06-04 11:41       ` Nick Roberts
2005-06-06 20:44         ` Nick Roberts
2005-06-11  5:54           ` Nick Roberts
2005-06-11  6:50           ` [PATCH] -data-list-changed-registers (Take 2) Nick Roberts
2005-06-13  2:40             ` Daniel Jacobowitz
2005-06-13  4:47               ` Nick Roberts
2005-06-13 13:48                 ` Daniel Jacobowitz
2005-06-13 22:38                   ` Nick Roberts
2005-06-13 22:42                     ` Daniel Jacobowitz
2005-06-14  2:45                       ` Nick Roberts
2005-06-17  1:51                         ` Daniel Jacobowitz
2005-06-17  3:13                           ` Nick Roberts [this message]
2005-06-17  3:22                             ` Daniel Jacobowitz

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=17074.16470.814479.200726@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --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