Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Readline 5.1 import
Date: Mon, 10 Apr 2006 18:30:00 -0000	[thread overview]
Message-ID: <17466.41960.90089.106620@localhost.redhat.com> (raw)
In-Reply-To: <20060410180030.GA29115@nevyn.them.org>


Daniel Jacobowitz writes:
 > I've locally imported readline 5.1 into src, replacing our older readline
 > 4.3 import.  It requires only two small changes in gdb (both dealing with
 > the rename of rluser.texinfo -> rluser.texi); patch attached.  I've also
 > attached a diff between readline 5.1 + upstream patches 001-004, and
 > my imported directory; I don't know how else I can usefully present the
 > changes, since a diff from the previous version of readline is too huge to
 > be useful.
 > 
 > I've done my best to preserve every local change.  The local changes are
 > mainly for Cygwin, DJGPP, and MinGW32; I tested GNU/Linux, and did manual
 > testing on both Cygwin and MinGW32.  My last attempt to build a DJGPP GDB
 > took all day and failed horribly due to GCC bugs, so I'm afraid I can't
 > test the __MSDOS__ bits.  But they're pretty straightforward and I did
 > preserve all the local ones.
 > 
 > Does anyone mind my committing the merge?  I'll be glad to help straighten
 > out any problems arising from that.  If you'd like to test it first, let
 > me know; it's a bit of work to produce a patched source tree.


Pls, make sure you do an import, not just a merge.  I don't remember
the detailed procedure, and I don't have my notes here, but the import
was first done on a branch and various tags were used:

readline-pre-43-import 
readline_4_3-import-branch
readline_4_3-import-branchpoint 
readline_4_3






  reply	other threads:[~2006-04-10 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 18:00 Daniel Jacobowitz
2006-04-10 18:30 ` Elena Zannoni [this message]
2006-04-10 18:40   ` Daniel Jacobowitz
2006-04-10 18:54     ` Elena Zannoni
2006-04-10 18:57       ` Daniel Jacobowitz
2006-04-20 17:32         ` Daniel Jacobowitz
2006-04-20 20:43           ` Elena Zannoni
2006-04-21  1:16             ` Jim Blandy
2006-04-21 13:25               ` Elena Zannoni
2006-04-24 22:10             ` Daniel Jacobowitz
2006-05-01 13:56               ` Daniel Jacobowitz
2006-05-05 18:26                 ` Daniel Jacobowitz
2006-04-10 19:04 ` Eli Zaretskii

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=17466.41960.90089.106620@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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