public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: DevilKin <devilkin-lkml@blindguardian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 bitkeeper repository
Date: Fri, 22 Feb 2002 10:40:15 -0500	[thread overview]
Message-ID: <3C76665F.F5DFA97F@mandrakesoft.com> (raw)
In-Reply-To: <20020222160657.A7914@caldera.de> <3C766020.FFC64A87@mandrakesoft.com> <20020222152723Z292901-890+3795@vger.kernel.org>

DevilKin wrote:
> On Friday 22 February 2002 16:13, Jeff Garzik wrote:
> > As a temporary measure people can pull from
> >       http://gkernel.bkbits.net/marcelo-2.4
> 
> Corrected URL: http://gkernel.bkbits.net:XXXX/marcelo-2.4
> 
> (you forgot the BK port, Jeff)


nope, "bk pull http://gkernel.bkbits.net/marcelo-2.4" or "bk clone ..."
works just fine without the port.


-- 
Jeff Garzik      | "UNIX enhancements aren't."
Building 1024    |           -- says /usr/games/fortune
MandrakeSoft     |

  reply	other threads:[~2002-02-22 15:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 15:06 Linux 2.4 bitkeeper repository Christoph Hellwig
2002-02-22 15:13 ` Jeff Garzik
2002-02-22 15:26   ` DevilKin
2002-02-22 15:40     ` Jeff Garzik [this message]
2002-02-22 15:44     ` Stelian Pop
2002-02-22 16:36   ` Marcelo Tosatti
2002-02-22 18:42     ` Larry McVoy
2002-02-22 19:37       ` Rik van Riel
2002-02-22 19:45         ` Larry McVoy
2002-02-23 19:40           ` Linus Torvalds
2002-02-22 16:53 ` Larry McVoy
2002-02-22 19:26 ` Rik van Riel
2002-02-22 19:37   ` Tom Rini
2002-02-22 19:49     ` Rik van Riel
2002-02-23  0:35       ` Tom Rini
2002-02-23  1:32         ` Larry McVoy
2002-02-23  1:46           ` Davide Libenzi
2002-02-23  1:58             ` 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=3C76665F.F5DFA97F@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=devilkin-lkml@blindguardian.org \
    --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