public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Jasper Spaans <jasper@vs19.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to fix timestamps in bk repo?
Date: Fri, 4 Jun 2004 08:56:13 -0700	[thread overview]
Message-ID: <20040604155613.GA1761@work.bitmover.com> (raw)
In-Reply-To: <20040604081926.GA24427@spaans.vs19.net>

On Fri, Jun 04, 2004 at 10:19:26AM +0200, Jasper Spaans wrote:
> Is it possible to reset the (BK-)timestamps on the following files in the
> http://linus.bkbits.net:8080/linux-2.5 repository? Somehow, they've gotten a
> timestamp which lies in the future, causing lots of warnings when I use a bk
> exported tree.

Sorry, the timestamps are part of the BK metadata and there isn't any way
to alter them after the fact.  

I'd suggest you not use the -T option to export or write a script that 
looks for timestamps in the future and fix them.

For everyone else, please keep your clocks in sync.  Whoever generated
these deltas must be running a very old version of BK (which is a license
violation by the way [whoohoo, we can now have 3 weeks of flames about
that horrible BK license that if people were obeying this wouldn't
have happened]).  Current versions of BK insist that your clock isn't
off by more than 24 hours (I suspect that this works only if you have
a net connection though, I don't remember).
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

  parent reply	other threads:[~2004-06-04 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04  8:19 how to fix timestamps in bk repo? Jasper Spaans
2004-06-04 15:34 ` Jeff Garzik
2004-06-04 15:56 ` Larry McVoy [this message]
2004-06-04 18:05   ` Jasper Spaans

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=20040604155613.GA1761@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=jasper@vs19.net \
    --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