mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hank Leininger <linux-kernel@progressive-comp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BK kernel commits list
Date: Wed, 9 Oct 2002 17:05:22 -0400	[thread overview]
Message-ID: <200210092105.g99L5MB17433@marc2.theaimsgroup.com> (raw)

On 2002-10-09, "David S. Miller" <davem@redhat.com> wrote: 
 
> I've created: 
>     bk-commits-head@vger.kernel.org 
>     bk-commits-24@vger.kernel.org 
 
FYI, I added these to the MARC list archives: 
 
http://marc.theaimsgroup.com/?l=bk-commits-head&r=1&w=2 
http://marc.theaimsgroup.com/?l=bk-commits-24&r=1&w=2 
 
...Sometime last night, so they've got all of today's traffic. 
 
-- 
Hank Leininger <hlein@progressive-comp.com>  
   

             reply	other threads:[~2002-10-09 20:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 21:05 Hank Leininger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-06  9:06 New BK License Problem? Jeff Garzik
2002-10-08 21:13 ` David Woodhouse
2002-10-08 22:15   ` David Woodhouse
2002-10-09  0:51     ` BK kernel commits list David S. Miller
2002-10-09 11:49       ` Skip Ford
2002-10-09 11:58         ` David S. Miller
2002-10-09 12:17         ` David Woodhouse
2002-10-09 12:12           ` David S. Miller
2002-10-09 14:11           ` Jeff Garzik
2002-10-09 14:44             ` Ben Collins
2002-10-09 14:55             ` David Woodhouse
2002-10-09 14:58               ` Ben Collins
2002-10-09 19:48               ` Jeff Garzik
2002-10-09 19:59                 ` Robert Love
2002-10-09 20:32                   ` Skip Ford
2002-10-09 20:34                   ` Jeff Garzik
2002-10-09 19:59                 ` Ben Collins
2002-10-09 20:52                 ` David Woodhouse
2002-10-09 21:02                   ` Robert Love
2002-10-09 20:41               ` David Woodhouse

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=200210092105.g99L5MB17433@marc2.theaimsgroup.com \
    --to=linux-kernel@progressive-comp.com \
    --cc=hlein@progressive-comp.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

all inboxes | Powered by JetHome®