From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com, jan.kratochvil@redhat.com, gdb@sourceware.org,
ktietz@redhat.com
Subject: Re: readline rebase 5.1->6.2?
Date: Sun, 03 Apr 2011 03:01:00 -0000 [thread overview]
Message-ID: <83sju0vy1k.fsf@gnu.org> (raw)
In-Reply-To: <83y63tvtd2.fsf@gnu.org>
> Date: Sat, 02 Apr 2011 13:29:45 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: jan.kratochvil@redhat.com, gdb@sourceware.org, ktietz@redhat.com
>
> > From: Tom Tromey <tromey@redhat.com>
> > Cc: jan.kratochvil@redhat.com, gdb@sourceware.org, ktietz@redhat.com
> > Date: Fri, 01 Apr 2011 08:19:32 -0600
> >
> > >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> >
> > Eli> The question is, what should we do about these patches? Submitting
> > Eli> them to upstream readline would be the best course (assuming the
> > Eli> readline maintainer is willing to include them), but that means we
> > Eli> will have to either wait for the next readline release or keep our
> > Eli> local patches for the time being.
> >
> > Yes, submit them. It is ok if it takes a while for the new readline to
> > reach our tree. The result can't be worse than our current situation.
>
> I sent a private mail to the readline maintainer with the patches.
> Let's see what he replies, and take it from there.
Chet agreed:
> Sure, I'll look at applying the patches. They'll be in the next readline
> release.
So we can now act on the assumption that the DJGPP-related patches to
readline are no longer an issue.
Note that I didn't do anything about the MinGW patches. I suggest
that their author(s) submit them to readline.
next prev parent reply other threads:[~2011-04-03 3:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 15:43 Jan Kratochvil
2011-03-22 16:43 ` Joel Brobecker
2011-03-22 16:58 ` Tom Tromey
2011-03-22 17:19 ` Kai Tietz
2011-03-22 19:05 ` Eli Zaretskii
2011-03-22 19:48 ` Jan Kratochvil
2011-03-22 19:59 ` Eli Zaretskii
2011-04-01 9:30 ` Eli Zaretskii
2011-04-01 14:19 ` Tom Tromey
2011-04-02 10:29 ` Eli Zaretskii
2011-04-03 3:01 ` Eli Zaretskii [this message]
2011-04-25 16:05 ` Jan Kratochvil
2011-04-02 20:10 ` Jan Kratochvil
2011-03-22 20:04 ` Tom Tromey
2011-04-01 9:25 ` Eli Zaretskii
2011-03-22 20:36 ` Joel Brobecker
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=83sju0vy1k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ktietz@redhat.com \
--cc=tromey@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