From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFC: Readline 5.1 import
Date: Thu, 20 Apr 2006 20:43:00 -0000 [thread overview]
Message-ID: <17479.61920.803213.910287@localhost.redhat.com> (raw)
In-Reply-To: <20060420173208.GM11710@nevyn.them.org>
FWIW when you leave things open ended, and say you are in no hurry and
going to wait, please, before pointing fingers, specify what time
frame you are thinking of. I cannot read your mind.
We do already have a branch named FSF where the readline imports have
been done before. The same branch has ben used for importing pristine
versions of texinfo. It seems the people you have asked must not be
used to track code from 3rd parties, and are willing to cut corners.
Anyway, I have prepared things for you to do the real merge. I have
- imported 5.1 on the fsf branch.
- Tagged the readline sources
- created a branch for the merge to happen there.
What you need to do now is check out the branch
readline_5_1-import-branch for gdb+dejagnu
then do
cvs update -jFSF:yesterday -jFSF src/readline
resolve the conflicts, cvs add new files, cvs rm files (and
directories), and commit. I would suggest letting a few others give it
a spin on the branch with exotic architectures, then merge everything
into mainline in a single swoop. Note that you need to delete
yourself the files that have disappeared from readline between 4.3 and
5.1 if any, cvs will not do that automatically.
next prev parent reply other threads:[~2006-04-20 20:43 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
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 [this message]
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=17479.61920.803213.910287@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