From: Larry McVoy <lm@bitmover.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: BK reader/writer locking
Date: Fri, 7 Jan 2000 12:42:29 -0800 [thread overview]
Message-ID: <200001072042.MAA24660@work.bitmover.com> (raw)
mea culpa. I had writer locks at the repository level working but not
reader locks. So you could get inconsistent data if you did a pull or
a resync while someone else was pushing.
A pass at fixing this is in hq.fsmlabs.com:/home/lm/bk so please pull that
to your local machine and "cd src; make production". This has already been
done on hq so you should be back in business on the shared repository.
By the way, I dunno if you know it, but you guys rate pretty much 24x7
support. Here's how to get it:
a) ALWAYS send help requests to dev@bitmover.com - contrary to public
opinion, BK is not just me. Andrew, Rick, Kim, and Aaron also
work here and are good and helping and fixing bugs.
b) If you don't get an ACK pretty quickly, and you are being held up,
you can call my business line which is in the US at 415-401-8808.
If you are stalled and you are sure it is a BK problem, for the time
being you can call 24 hours/day, I'll get up. I know some of you are
in Europe so I pretty much have to deal with the timezone difference.
Cheers,
--lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-01-07 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200001072042.MAA24660@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linuxppc-dev@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).