From: Larry McVoy <lm@bitmover.com>
To: Paul.Clements@steeleye.com
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Pavel Machek <pavel@ucw.cz>, John Levon <levon@movementarian.org>,
kernel list <linux-kernel@vger.kernel.org>,
Larry McVoy <lm@bitmover.com>
Subject: Re: bkcvs not up-to-date?
Date: Sat, 10 May 2003 08:21:20 -0700 [thread overview]
Message-ID: <20030510152120.GA24310@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10305072233360.15498-100000@clements.sc.steeleye.com>
This should be fixed now. We had a bad disk on kernel.bkbits.net.
On Wed, May 07, 2003 at 10:36:42PM -0400, Paul Clements wrote:
> On Thu, 8 May 2003, Carl-Daniel Hailfinger wrote:
> >
> > Pavel Machek wrote:
> > >
> > >>>and checked out the tree, but cvs log Makefile still indicates 2.5.68
> > >>>is the lastest version. What am I doing wrong?
> > >>
> > >>I have the same problem, the CVS gateway got stuck some point in the
> > >>middle of 2.5.68 and has had no apparen t updates since
> > >
> > >
> > > Its even worse: part of updates gets there. Like CREDITS file is
> > > up-to-date but Makefile is not.
>
> Yeah, I'm getting errors trying to load loop.ko, that looks kind of
> suspicious...loop has been working...of course I guess it could be the
> regularly scheduled breakage...
>
> --
> Paul
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-05-10 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 11:15 bkcvs not up-to-date? Pavel Machek
2003-05-07 11:57 ` John Levon
2003-05-07 23:16 ` Pavel Machek
2003-05-08 1:03 ` Carl-Daniel Hailfinger
2003-05-08 2:36 ` Paul Clements
2003-05-10 15:21 ` Larry McVoy [this message]
2003-05-10 17:47 ` Pavel Machek
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=20030510152120.GA24310@work.bitmover.com \
--to=lm@bitmover.com \
--cc=Paul.Clements@steeleye.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.