From: Larry McVoy <lm@bitmover.com>
To: "James H. Cloos Jr." <cloos@jhcloos.com>, linux-kernel@vger.kernel.org
Subject: Re: bk://linux.bkbits.net/linux-2.5
Date: Sat, 2 Aug 2003 19:57:39 -0700 [thread overview]
Message-ID: <20030803025739.GA25545@work.bitmover.com> (raw)
In-Reply-To: <20030802165027.A13947@flint.arm.linux.org.uk>
On Sat, Aug 02, 2003 at 04:50:28PM +0100, Russell King wrote:
> On Sat, Aug 02, 2003 at 11:26:09AM -0400, James H. Cloos Jr. wrote:
> > $SUB is not getting updated. There are over 200 csets in
> > bk://linus.bkbits.net/linux-2.5 that have not made it over.
> > ^
> > I've not checked whether they show up in the cvs or svn repos.
>
> Try bothering support@bitmover.com rather than lkml - they have the power
> to fix the problem unlike lkml.
I'll sort through these problems when I get back in town tomorrow if they
haven't been fixed by then. The BK2CVS tree is apparently not getting
updated either, expect that to be back on line monday.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-08-03 2:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 15:26 bk://linux.bkbits.net/linux-2.5 James H. Cloos Jr.
2003-08-02 15:50 ` bk://linux.bkbits.net/linux-2.5 Russell King
2003-08-03 2:57 ` Larry McVoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-09 1:33 bk://linux.bkbits.net/linux-2.5 Paul Mackerras
2002-03-09 2:35 ` bk://linux.bkbits.net/linux-2.5 Rik van Riel
2002-03-09 8:12 ` bk://linux.bkbits.net/linux-2.5 Russell King
2002-03-09 10:48 ` bk://linux.bkbits.net/linux-2.5 Jeff Garzik
2002-03-09 13:15 ` bk://linux.bkbits.net/linux-2.5 Rik van Riel
2002-03-09 12:38 ` bk://linux.bkbits.net/linux-2.5 Anton Altaparmakov
2002-03-11 16:43 ` bk://linux.bkbits.net/linux-2.5 Larry McVoy
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=20030803025739.GA25545@work.bitmover.com \
--to=lm@bitmover.com \
--cc=cloos@jhcloos.com \
--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 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.