From: Andy Isaacson <adi@hexapodia.org>
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: BAD gzip hdr on all 2.0 trees?
Date: Fri, 17 Dec 2004 21:43:46 -0800 [thread overview]
Message-ID: <20041218054346.GA23477@hexapodia.org> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD5117298@cacexc12.americas.cpqcorp.net>
On Fri, Dec 17, 2004 at 02:00:23PM -0800, Magenheimer, Dan wrote:
> I am bk-clone'ing not bk-pull'ing so parent is irrelevant,
> correct? (I rm'd earlier an 2.0 tree thinking that might
> have been the problem.)
Well, you don't have a parent until you have a repo. But if you still
have an old repo around, you can use that to bootstrap past the current
problems with bkbits[1]; I just upgraded an ancient xeno-unstable.bk
tree to xen-2.0.bk by the following:
% bk clone -ql xeno-unstable.bk xen-2.0.bk
% cd xen-2.0.bk
% bk parent bk://xen.bkbits.net/xen-2.0.bk
% bk pull
...
takepatch: 5242 new revisions, 0 conflicts in 698 files
...
% bk changes -L
%
That's a pretty sizable pull right there, and it worked perfectly.
> Also, why would it work with xeno-1.2.bk but not with the 2.0
> trees?
There's some issue on bkbits that's resulting in these problems. Might
be something like a full filesystem, or a wierd wedged process holding a
lock. But the whole point of BK's distributed system is that there
doesn't have to be a single-point-of-failure; you can get your
changesets from elsewhere and it doesn't matter to BK. And that
"elsewhere" can certainly be a local repo at a previous version.
[1] As far as I can tell, it's only a problem with clones, not with
pulls. Maybe it's just Larry's way of telling you "bootstrap from
your local clones, people!" :)
BK is *really* good at saving bandwidth and time this way. It
boggles my mind to see people cloning from bkbits all the time.
I don't think I've done a remote clone of any of the trees I follow
in *months*. Instead, I do a local clone, 'bk repogca', 'bk undo',
followed by pull.
-andy
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-18 5:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 22:00 BAD gzip hdr on all 2.0 trees? Magenheimer, Dan (HP Labs Fort Collins)
2004-12-18 5:43 ` Andy Isaacson [this message]
2004-12-18 21:21 ` start xen-ia64-devel or just use xen-devel? dan.magenheimer
-- strict thread matches above, loose matches on Subject: below --
2004-12-17 20:52 BAD gzip hdr on all 2.0 trees? Magenheimer, Dan (HP Labs Fort Collins)
2004-12-17 21:39 ` Andy Isaacson
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=20041218054346.GA23477@hexapodia.org \
--to=adi@hexapodia.org \
--cc=dan.magenheimer@hp.com \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.