From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.5 bk tree broken?
Date: Mon, 23 Jun 2003 22:52:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105640875132527@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105640820432133@msgid-missing>
Yes, what's there on bkbits.net is totally obsolete (5 weeks old!).
I know bkbits.net had a machine failure on Friday/Saturday.
BK folks: could you restore a recent version of the linux-ia64-2.5
repository?
Thanks,
--david
>>>>> On Mon, 23 Jun 2003 15:43:05 -0700, "Luck, Tony" <tony.luck@intel.com> said:
Tony> I did a "bk pull" from
Tony> http://lia64.bkbits.net:8080/linux-ia64-2.5
Tony> a few minutes ago, and was surprised when BitKeeper complained
Tony> about lots of merge collisions (the bk tree into which I
Tony> pulled hasn't even had a "bk edit" run in it, let alone any
Tony> changes checked in).
Tony> Since I'm a neophyte at BK, I tried my usual fix (remove the
Tony> whole tree, and run "bk clone" again). This succeeded without
Tony> any reported errors, but time seems to have gone
Tony> backwards. The tree I now see is missing some stuff that was
Tony> checked into 2.5.72 (e.g fixes to include/asm-ia64/mca.h and
Tony> arch/ia64/kernel/mca.h for cleaner handling of INIT events).
Tony> The Web interface to BK says the newest changeset in this tree
Tony> was applied 5 weeks ago.
Tony> -Tony - To unsubscribe from this list: send the line
Tony> "unsubscribe linux-ia64" in the body of a message to
Tony> majordomo@vger.kernel.org More majordomo info at
Tony> http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-06-23 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 22:43 2.5 bk tree broken? Luck, Tony
2003-06-23 22:52 ` David Mosberger [this message]
2003-06-23 23:09 ` David Mosberger
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=marc-linux-ia64-105640875132527@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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