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: Mon, 10 Apr 2006 18:54:00 -0000 [thread overview]
Message-ID: <17466.43406.495021.640065@localhost.redhat.com> (raw)
In-Reply-To: <20060410184010.GA30365@nevyn.them.org>
Daniel Jacobowitz writes:
> On Mon, Apr 10, 2006 at 02:28:56PM -0400, Elena Zannoni wrote:
> > 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
>
> I guess you mean using "cvs import" and vendor branches.
>
Yes.
> I can do that, but I'd appreciate any advice; I've never managed to get
> cvs imports to behave properly, and I don't have my head wrapped around
> how it's supposed to work. What's the advantage over just correcting
> HEAD?
>
It's a cleaner process, and you can keep track of your local patches
on top of the original imported version. I can send you notes later
tonight on how to do it, I don't have them with me at work.
Here is what I did for the last import, but it doesn't help much.
http://sourceware.org/ml/gdb/2002-08/msg00317.html
next prev parent reply other threads:[~2006-04-10 18:54 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 [this message]
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.43406.495021.640065@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