linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Rik van Riel <riel@conectiva.com.br>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: bk://linux.bkbits.net/linux-2.5
Date: Sat, 09 Mar 2002 05:48:39 -0500	[thread overview]
Message-ID: <3C89E887.D8B9E6C1@mandrakesoft.com> (raw)
In-Reply-To: <15497.26229.778087.419723@argo.ozlabs.ibm.com> <Pine.LNX.4.44L.0203082333380.2181-100000@imladris.surriel.com> <20020309081255.A26922@flint.arm.linux.org.uk>

Russell King wrote:
> 
> On Fri, Mar 08, 2002 at 11:35:11PM -0300, Rik van Riel wrote:
> > For now I've put up the 2.5 tree on bk://linuxvm.bkbits.net/linus-2.5
> 
> Jeff also does this - http://gkernel.bkbits.net/linus-2.5
> 
> Seems a little wasteful to have multiple trees of the same thing available
> from the same place.

Rik thinks that a cron job will somehow notice Linus updates faster than
I do :)

-- 
Jeff Garzik      | Usenet Rule #2 (John Gilmore): "The Net interprets
Building 1024    | censorship as damage and routes around it."
MandrakeSoft     |

  reply	other threads:[~2002-03-09 10:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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     ` Jeff Garzik [this message]
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
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   ` 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=3C89E887.D8B9E6C1@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@transmeta.com \
    /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).