From: Larry McVoy <lm@bitmover.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Pantelis Antoniou <panto@intracom.gr>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Problem with bitkeeper?
Date: Thu, 27 May 2004 07:40:10 -0700 [thread overview]
Message-ID: <20040527144010.GA3375@work.bitmover.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0405271206490.17038@waterleaf.sonytel.be>
On Thu, May 27, 2004 at 12:07:18PM +0200, Geert Uytterhoeven wrote:
>
> On Thu, 27 May 2004, Pantelis Antoniou wrote:
> > Is anyone else having problems pulling today from
> > from ppc.bkbits.net (using http)?
>
> bkbits.net is down, cfr. a posting from Larry on lkml.
It's fixed. It was fixed last night and a trigger we had put in earlier
to log BK versions (so we know if we need to nag people to upgrade)
was broken.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-05-27 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 9:25 Problem with bitkeeper? Pantelis Antoniou
2004-05-27 10:07 ` Geert Uytterhoeven
2004-05-27 14:40 ` Larry McVoy [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=20040527144010.GA3375@work.bitmover.com \
--to=lm@bitmover.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=panto@intracom.gr \
/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;
as well as URLs for NNTP newsgroup(s).