public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: kernel CVS is malfunctioning
Date: Sat, 4 Dec 2004 04:27:23 +0100	[thread overview]
Message-ID: <20041204032723.GX32635@dualathlon.random> (raw)

The kernel CVS seems screwed. cvsps -x --bkcvs tells there are 2
checkins.

cvsps -x for days showed this as the last checkin.

WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
WARNING: non-increasing dates in encountered patchset members
[..]
---------------------
PatchSet 81424
Date: 1970/01/01 01:33:24
Author: zwane
Branch: HEAD
Tag: (none)
Log:
x86: move PIT code to timer_pit

(Logical change 1.21009)

Members:
        arch/i386/kernel/i8259.c:1.35->1.36
        arch/i386/kernel/timers/timer_pit.c:1.14->1.15
        include/asm-i386/timer.h:1.15->1.16

(see the Date tag too)

Perhaps I'm the only user, I use it on a daily basis, it worked fine
until a few days ago.

             reply	other threads:[~2004-12-04  3:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04  3:27 Andrea Arcangeli [this message]
     [not found] ` <fa.i7vl3ki.m0gsji@ifi.uio.no>
2004-12-04 17:40   ` kernel CVS is malfunctioning Håvard Kvålen
2004-12-04 17:50     ` Andrea Arcangeli
2004-12-05  2:42     ` H. Peter Anvin

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=20041204032723.GX32635@dualathlon.random \
    --to=andrea@suse.de \
    --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