From: Larry McVoy <lm@bitmover.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Larry McVoy <lm@bitmover.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK] disconnected operation
Date: Sun, 26 Dec 2004 10:35:41 -0800 [thread overview]
Message-ID: <20041226183541.GA28952@work.bitmover.com> (raw)
In-Reply-To: <1104085546.5268.38.camel@mulgrave>
> OK, I cloned a new repository and started applying patches to it. The
> transcript of what I did is attached. You can see that after I
> disconnect from the network, I get three emails imported before it spits
> an error at me.
OK, cool. We can keep going back and forth or if you wish you can send me
the mailbox of patches and the cset key to which they should be applied
and I'll try it.
Can you do a "bk lease renew" before you start the process, then do a
"bk lease show" to make sure it took? When it starts to fail I'd like
to know what time your computer thinks it is. Is it possible that you
are using your net connection to maintain your date and then when you
disconnect your date warps forward? Does this always happen at the
3rd commit?
Thanks!
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2004-12-26 18:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 16:12 lease.openlogging.org is unreachable James Bottomley
2004-12-26 16:27 ` Larry McVoy
2004-12-26 16:43 ` James Bottomley
2004-12-26 17:19 ` [BK] disconnected operation Larry McVoy
2004-12-26 18:25 ` James Bottomley
2004-12-26 18:35 ` Larry McVoy [this message]
2004-12-26 18:46 ` James Bottomley
2004-12-26 18:41 ` Zwane Mwaikambo
2004-12-26 20:30 ` Martin Dalecki
2004-12-26 20:20 ` Martin Dalecki
2004-12-28 14:33 ` Ricky Beam
2004-12-29 5:16 ` Kyle Moffett
2004-12-29 6:00 ` Ricky Beam
2004-12-28 9:17 ` Marcelo Tosatti
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=20041226183541.GA28952@work.bitmover.com \
--to=lm@bitmover.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@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