public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: "J . A . Magallon" <jamagallon@able.es>,
	Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel archives format
Date: Mon, 30 Jul 2001 02:30:26 +0200	[thread overview]
Message-ID: <01073002302602.01194@starship> (raw)
In-Reply-To: <20010730013504.A1418@werewolf.able.es>
In-Reply-To: <20010730013504.A1418@werewolf.able.es>

On Monday 30 July 2001 01:35, J . A . Magallon wrote:
> A recent message that asked for the use-once patch and the answer
> ('look for in on the archives') reminded me a comment I wanted to do.
>
> Nowadays looking for a patch in almost all kernel archives is
> useless. You get pages formatted in HTML, and even page source can
> give you any info. Just a bunch of &nbsp; and &gt;, and without
> blanks nor any rest of the original formatting of the patch.
>
> The only archive I have found to get the correct info is the one
> pointed in the vger 'list of lists':
> http://marc.theaimsgroup.com/?l=linux-kernel

Yes, marc's "download raw" is a godsend.  Unfortunately, marc's search 
isn't very good, so I sometimes find myself searching one of the 
hypermail archives just to find the date/time/author then getting the 
raw download from marc.

It would be nice to see an official corporate sponsor step up to the 
plate to provide funding for a really definitive archive site.  Two 
features I'd like to see:

  - Google-quality archive search engine
  - Download multiple messages in mbox format for offline reading

--
Daniel

  reply	other threads:[~2001-07-30  0:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-29 23:35 kernel archives format J . A . Magallon
2001-07-30  0:30 ` Daniel Phillips [this message]
2001-07-30  2:29   ` Ben Ford

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=01073002302602.01194@starship \
    --to=phillips@bonn-fries.net \
    --cc=jamagallon@able.es \
    --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