Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: msnyder@sonic.net
To: msnyder@sonic.net, "Jim Blandy" <jimb@codesourcery.com>,
	        gdb-patches@sourceware.org, bug-readline@gnu.org
Subject: Re: PATCH: readline/histexpand.c, resource leak
Date: Wed, 15 Aug 2007 01:40:00 -0000	[thread overview]
Message-ID: <11655.12.7.175.2.1187142010.squirrel@webmail.sonic.net> (raw)
In-Reply-To: <20070815012021.GA14714@caradoc.them.org>

> On Tue, Aug 14, 2007 at 05:37:47PM -0700, Michael Snyder wrote:
>> By the way, are we maintaining our own readline fork?
>> Should I check these in locally?
>
> No, we are not.  Or rather, we sort of are, but we're trying not to.
> I believe the only patches in our version are build related and DOS
> and/or Windows related ones that I didn't really grok; everything else
> has been merged.
>
> Personally, I would be happy to remove the directory entirely, but I'm
> sure that would inconvenience some people.  I use the system readline
> to build Debian GDB packages.

OK, well I heard from Chet Ramey to the effect that he had already
checked these in to his sources (or at least, the parts of them that
he wanted) -- so I guess I'll just let it go at that until the next
time we merge (or whatever we do).




  reply	other threads:[~2007-08-15  1:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  2:14 msnyder
2007-08-10 21:32 ` msnyder
2007-08-15  0:01 ` Jim Blandy
2007-08-15  0:38   ` msnyder
2007-08-15  1:20     ` Daniel Jacobowitz
2007-08-15  1:40       ` msnyder [this message]
2007-08-15 21:43     ` Jim Blandy
2007-08-18 20:12   ` [Bug-readline] " Chet Ramey
2007-08-18 20:15     ` msnyder
2007-08-20 17:03     ` Jim Blandy
2007-08-22  2:02       ` Chet Ramey

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=11655.12.7.175.2.1187142010.squirrel@webmail.sonic.net \
    --to=msnyder@sonic.net \
    --cc=bug-readline@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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