Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix build with Python 3.4 (PR python/16784)
Date: Fri, 05 Dec 2014 23:07:00 -0000	[thread overview]
Message-ID: <54823AA4.7080902@redhat.com> (raw)
In-Reply-To: <87h9x9d7nf.fsf@redhat.com>

On 12/05/2014 03:00 PM, Sergio Durigan Junior wrote:
> On Friday, December 05 2014, Simon Marchi wrote:
>
>>>> I changed the signature of deprecated_readline_hook. I would've changed any
>>>> user of it, but it seems like nothing is using it,
>>>
>>> You'd probably find it in the insight/gdbtk code.
>>
>> Is this something that I need to update, or insight is not maintained anymore?
>
> Insight is maintained by Keith Seitz (Cc'ed in this message).  My first
> reaction is that it would be good if you updated it.

As reported elsewhere, Insight is a bit in limbo right now as I try to 
figure out how to best deal with gdb moving to git (and start my own 
migration).

There is a temporary repository set up by the Fedora packaging 
maintainer, Patrick Monnerat. I believe this was also referenced earlier.

IMO, I would take that as the official repository for the time being.

You can update it, or I can. It's not a huge deal; just let me know.

Keith


  reply	other threads:[~2014-12-05 23:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1417009634-2356-1-git-send-email-simon.marchi@ericsson.com>
2014-12-04 18:15 ` Pedro Alves
2014-12-05 21:49   ` Simon Marchi
2014-12-05 23:00     ` Sergio Durigan Junior
2014-12-05 23:07       ` Keith Seitz [this message]
2014-12-08 16:22         ` Simon Marchi
2014-12-08 17:50           ` Patrick Monnerat
2014-12-16 11:20           ` Patrick Monnerat
2014-12-08 16:44   ` Simon Marchi
2014-12-12 15:02     ` Pedro Alves

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=54823AA4.7080902@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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