public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK] disconnected operation
Date: Sun, 26 Dec 2004 12:46:32 -0600	[thread overview]
Message-ID: <1104086792.5268.43.camel@mulgrave> (raw)
In-Reply-To: <20041226183541.GA28952@work.bitmover.com>

On Sun, 2004-12-26 at 10:35 -0800, Larry McVoy wrote:
> 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.

That might be easier, since BK operations take a large amount of time on
my laptop.  I'll send you the emails under separate cover.

> 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?

I did do a bk lease renew at the top (in the log).  My clock is
controlled by NTP, but it just syncs to the localhost fudge when it
loses all net connection.  The time doesn't jump when this happens (it
does drift by a few hundred milliseconds every hour or so I remain
disconnected, though).

Where it happens seems to be variable.  Most often it's the first or
second commit.

James



  reply	other threads:[~2004-12-26 18:46 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
2004-12-26 18:46           ` James Bottomley [this message]
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=1104086792.5268.43.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    /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