From: Larry McVoy <lm@bitmover.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Larry McVoy <lm@bitmover.com>, Linus Torvalds <torvalds@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Problem with linux-2.6 BK repository on BKbkits?
Date: Mon, 22 Nov 2004 08:02:46 -0800 [thread overview]
Message-ID: <20041122160246.GA3683@work.bitmover.com> (raw)
In-Reply-To: <1101122708.18623.16.camel@imp.csi.cam.ac.uk>
On Mon, Nov 22, 2004 at 11:25:08AM +0000, Anton Altaparmakov wrote:
> [snip]
> Applying 1 revisions to net/ipv4/netfilter/ipt_CLUSTERIP.c
> fk cache: insert error for johnrose@austin.ibm.com[greg]|
> drivers/pci/hotplug/rpaphp_pci.c|20210428163018
> insert: File exists
> Applying 1 revisions to drivers/pci/hotplug/rpaphp_pci.c
> [snip]
It's pretty harmless and will be fixed in 3.2.4 (due out pretty soon).
It's a legacy thing from the very early days of BK and the only BK tree
which makes use of it is the BK source tree itself so we dropped it.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
prev parent reply other threads:[~2004-11-22 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 11:25 Problem with linux-2.6 BK repository on BKbkits? Anton Altaparmakov
2004-11-22 16:02 ` Larry McVoy [this message]
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=20041122160246.GA3683@work.bitmover.com \
--to=lm@bitmover.com \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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