public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Make kernel.bkbits.net public via web? [was Re: kernel.bkbits.net and BK->CVS gateway]
Date: Sun, 11 May 2003 11:45:51 -0400	[thread overview]
Message-ID: <3EBE702F.3020709@myrealbox.com> (raw)
In-Reply-To: 20030510140455.GA23475@work.bitmover.com

Larry McVoy wrote:
> Try #2, first one didn't seem make it.
> 
> ----- Forwarded message from Linux Kernel Mailing List <linux-kernel@vger.kernel.org> -----
> 
> Date: Fri, 9 May 2003 19:46:13 -0700
> From: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Cc: hpa@transmeta.com, davem@redhat.com
> Subject: kernel.bkbits.net and BK->CVS gateway
> 
> We replaced the bad drive and are restoring home directories.
> Once we have the restore done, we'll turn on people's accounts again.
> We are shutting off nightly backups for a few days so that we have 
> the backups to cherry pick any missing config files, etc.

[SNIP]

Larry,

I was wondering if you would considier putting a bkbits web frontend on 
kernel.bkbits.net.  I can think of a few cases where it might come in 
handy.  For example, one of the devs is too busy (understandably) to 
roll a patch at a given point in time and states in response to a bug 
report that (s)he'll get linus to pull the fixes later on.  In this 
case, people who like to live dangerously and don't want to wait might 
take it upon themselves to surf over to kernel.bkbits.net and download 
the ChangeSet rather than cloning an *entire* tree just to get it.  I 
suppose this would also serve as a means for people who do not (or 
cannot) use bitkeeper to get said ChangeSet.

Cheers,
Nicholas



      parent reply	other threads:[~2003-05-11 15:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 14:04 kernel.bkbits.net and BK->CVS gateway Larry McVoy
2003-05-10 15:34 ` Ben Collins
2003-05-10 16:06   ` Larry McVoy
2003-05-10 15:43     ` Ben Collins
2003-05-10 16:22       ` Larry McVoy
2003-05-10 19:23         ` Jan Harkes
2003-05-10 19:55           ` Larry McVoy
2003-05-10 20:21             ` Roman Zippel
2003-05-10 20:42               ` David S. Miller
2003-05-10 20:59                 ` Roman Zippel
2003-05-10 20:01                   ` David S. Miller
2003-05-10 21:15                     ` Roman Zippel
2003-05-10 20:44               ` Larry McVoy
2003-05-10 21:28             ` Roman Zippel
2003-05-10 21:43         ` Ben Collins
2003-05-11 15:45 ` Nicholas Wourms [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=3EBE702F.3020709@myrealbox.com \
    --to=nwourms@myrealbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox