public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Andrew Burgess" <aburgess@broadcom.com>
To: insight@sourceware.org,	"Keith Seitz" <keiths@redhat.com>
Subject: Re: [PATCH] Remove use of deprecated_command_loop_hook
Date: Thu, 05 Sep 2013 13:00:00 -0000	[thread overview]
Message-ID: <52288050.6060800@broadcom.com> (raw)
In-Reply-To: <52287F7D.6040308@broadcom.com>

On 05/09/2013 1:56 PM, Andrew Burgess wrote:
> On 04/09/2013 11:17 PM, Keith Seitz wrote:
>> Sorry for the delay on this: I've been out of the office for a bit.
>>
>> On 08/21/2013 05:11 PM, Andrew Burgess wrote:
>>> I have commit access to gdb, but I have no idea if that extends to
>>> gdb/gdbtk, and even if it did I obviously wouldn't commit without
>>> approval :)
>>
>> I handle insight as an extension of gdb. Pretty much the same policies
>> w.r.t. obvious patches, build errors, etc. If you have
>> commit-after-approval on gdb, you do here, too.
>>
>>> What do you think?
>>
>> I actually wonder how something this simple has been overlooked for so
>> long? Well, actually, I do know. Thank you for thinking about us!
>>
>> Please commit.
> 
> Committed.

Gah! The date I used in the ChangeLog was the original date I posted the
patch, not the date I actually made the commit.

Given that this date is still later than the previous change in the file
I'm going to leave it alone, unless I'm asked to change it.

Sorry for that.

Andrew

      reply	other threads:[~2013-09-05 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22  0:11 Andrew Burgess
2013-09-04 22:17 ` Keith Seitz
2013-09-05 12:56   ` Andrew Burgess
2013-09-05 13:00     ` Andrew Burgess [this message]

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=52288050.6060800@broadcom.com \
    --to=aburgess@broadcom.com \
    --cc=insight@sourceware.org \
    --cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).