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

On Fri, Jun 04, 2004 at 08:56:13AM -0700, Larry McVoy 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.  

Ack. I just tried something with the following result:

---8<---
# This is a BitKeeper generated diff -Nru style patch.
#
# drivers/base/class.c
#   2004/06/04 19:55:06+02:00 spaans@spaans.vs19.net +0 -1
#   Fix timestamp
# 
# drivers/base/class.c
#   2004/06/04 19:54:56+02:00 spaans@spaans.vs19.net +1 -0
# 
# ChangeSet
#   2004/06/04 19:55:32+02:00 spaans@spaans.vs19.net 
#   class.c:
#     Fix timestamp
# 
---8<---

Can anyone confirm that importing this does the trick? If so, I'll whip up
the 'patch' for all six files.

Regards,
-- 
Jasper Spaans                                       http://jsp.vs19.net/
 19:56:31 up 9970 days, 10:43, 0 users, load average: 6.19 6.08 5.67
  -... .- -.. --. . .-. -... .- -.. --. . .-. -... .- -.. --. . .-.

      reply	other threads:[~2004-06-04 18:05 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
2004-06-04 18:05   ` Jasper Spaans [this message]

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=20040604180503.GA14530@spaans.vs19.net \
    --to=jasper@vs19.net \
    --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