From: Oleg Verych <olecom@flower.upol.cz>
To: Ben Pfaff <blp@cs.stanford.edu>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
postmaster@vger.kernel.org, webguy@theaimsgroup.com,
postmaster@lkml.org, postmaster@ussg.iu.edu
Subject: Re: Request for Linux Kernel Mailing List archives
Date: Thu, 21 Jun 2007 08:21:03 +0200 [thread overview]
Message-ID: <E1I1G2R-00058L-JT@flower> (raw)
In-Reply-To: <87sl8mbioi.fsf@blp.benpfaff.org>
* Newsgroups: gmane.linux.kernel
* Date: Wed, 20 Jun 2007 11:10:53 -0700
>
>> For example, if a message had:
>>
>> Message-ID: <4676C78D.8040208@zytor.com>
>>
>> ... and I could just generate a URL:
>>
>> http://linux-kernel.example.com/msgid/4676C78D.8040208@zytor.com
>
> gmane can do that:
> http://mid.gmane.org/4676C78D.8040208@zytor.com
To have Gmane (news<=>e-mail [and web]) engine[s] on the kernel.org will
be the best thing ever!
The "News<=>e-mail" part is major because of things, i've learned after
using it with (_mature_ news reader) slrn. Any web interface, basic like
in marcs.info, or comprehensive, like Gmane's one can't replace
functionality news server(Gmane)/reader is giving to you (summary):
* You don't receive (or annoyingly bounce) huge traffic.
. big backlogs are handled easily in many cases, like getting
e-mails, replying in interesting threads, just don't care about
flames. I've just removed (by one key-press) 300, 200, 100 messages
of Dual-Licensing thread, because i trust Linus.
* Interesting discussions are easily saved(by threads) on your side, so
you can search them or read (any mbox format reader, like `mutt -f`)
* (slrn) Searching Message-Id as easy as one key-combination and one
copy/paste {1}
* (slrn) Restoring of whole thread from one e-mail (or {1}) -- one
key-combination
* (slrn + Gmane) headers have "Archived-At" entry, so i can just
copy/paste it for web-based users
* (slrn + Gmane) listing of news-groups (actually ML<=>Gmane-NEWS)
as easy as all above: patterns, one key-combination
* i bet much more, than i've just told.
And that's pretty why i'm happy to be with. After abandoning Mozilla
(buggy, memory hungry ever stuff), X and having console, screen, slrn,
lynx, emacs-nox i'm a pretty much more efficient that any time back.
All web, rss, other XML/WEB-2.0 crap does will not help. Get your
developers back -- use and publish healthy ways and tools to use!
I mean, come on, that's easy, rather than develop IMHO useless
e-mail/patch brokenness (WRT plain-text) checkers and docs.
Publish your way of being productive and saving environment! (tm:)
>> (Extra points if all the vger lists are available, not just LKML.)
>
> gmane has thousands of free software mailing lists. I don't know
> whether it has all of the vger lists.
There are many, that i'm aware of: kernel, commits, ide, net, usb,
archs(amd64 at least), sparse, git...
Namespace in Gmane is a little bit wrong. For example
gmane.linux.kernel and gmane.linux.debian.*
I.e. Linux kernel (with sub-parts) is in noise of distributions, while
latter can have different kernel actually (e.g. kfreebsd in the Debian).
____
next prev parent reply other threads:[~2007-06-21 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 15:37 H. Peter Anvin
2007-06-20 15:52 ` Björn Steinbrink
2007-06-20 15:57 ` H. Peter Anvin
2007-06-20 16:38 ` Hank Leininger
2007-09-12 10:27 ` Andreas Herrmann
2007-06-20 18:10 ` Ben Pfaff
2007-06-21 6:21 ` Oleg Verych [this message]
2007-06-21 14:36 ` Oleg Verych
2007-06-21 15:06 ` David Woodhouse
2007-06-21 15:54 ` Björn Steinbrink
2007-06-21 15:56 ` David Woodhouse
2007-06-21 16:00 ` H. Peter Anvin
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=E1I1G2R-00058L-JT@flower \
--to=olecom@flower.upol.cz \
--cc=blp@cs.stanford.edu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=postmaster@lkml.org \
--cc=postmaster@ussg.iu.edu \
--cc=postmaster@vger.kernel.org \
--cc=webguy@theaimsgroup.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
all inboxes | Powered by JetHome®