From: Wolfgang Denk <wd@denx.de>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc_2_4_devel from denx vs. bitkeeper
Date: Sat, 22 Feb 2003 21:19:01 +0100 [thread overview]
Message-ID: <20030222201906.E598CC6E0D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 21 Feb 2003 12:55:13 PST." <995FF289C9D69747A09E42992644595405B2367F@penguin.adic.com>
Dear Brian,
in message <995FF289C9D69747A09E42992644595405B2367F@penguin.adic.com> you wrote:
>
> How do you manage CVS and bk together? In other words, how do you pull
> bitkeeper updates into your CVS controlled source tree?
Simply: I don't. I tried several ways, but probably I don't
understand enough of BK to make it work reliably. So I just generate
patches between certain BK versions, which I then import into our
CVS.
> However, I ran a test to make sure this would work and ran into a problem.
> This is what I tested:
I tried similar things, and always ran into some cases where an
automatic approach would fail.
> Any words of wisdom??
Sorry, I'm neither a BK nor a CVS guru (but I manage to do my job
with CVS).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Faith may be defined briefly as an illogical belief in the occurence
of the improbable. - H. L. Mencken
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-02-22 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <995FF289C9D69747A09E42992644595405B2367F@penguin.adic.com>
2003-02-22 20:19 ` Wolfgang Denk [this message]
2003-02-21 16:02 linuxppc_2_4_devel from denx vs. bitkeeper brian.auld
2003-02-21 17:30 ` Wolfgang Denk
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=20030222201906.E598CC6E0D@atlas.denx.de \
--to=wd@denx.de \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).