mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Mailing lists (again, was ANNOUNCEMENT: Real-time Linux users list created)
Date: Sun, 22 Oct 2006 07:56:12 +0000 (UTC)	[thread overview]
Message-ID: <slrnejm9d6.30t.olecom@flower.upol.cz> (raw)
In-Reply-To: <E1GawZH-0002l3-FG@candygram.thunk.org>

Hallo, Theodore.

On 2006-10-20, Theodore Ts'o wrote:
>
> 	We have created a list for users of CONFIG_PREEMPT_RT,
> linux-rt-users@vger.kernel.org.   It is archived on gmane.org (and of
> course people who want to read it via gmane's NNTP or RSS feeds can do
> so as well): 
>
> 	http://gmane.org/info.php?group=gmane.linux.rt.user

Could you, please, explain why this new list and LKML add that
(imho silly) messages in every post? (e.g.):
.____
|-
|To unsubscribe from this list: send the line "unsubscribe
|linux-rt-users" in
|the body of a message to majordomo@vger.kernel.org
|More majordomo info at  http://vger.kernel.org/majordomo-info.html
`----

Why not to use something like this in the headers?

,--
|List-Post: <mailto:XXX-kernel@lists.ZZZZ.org>
|List-Help: <mailto:XXX-kernel-request@lists.ZZZZ.org?subject=help>
|List-Subscribe: <mailto:XXX-kernel-request@lists.ZZZZ.org?subject=su...
|List-Unsubscribe: <mailto:XXX-kernel-request@lists.ZZZZ.org?subject=un...
`--

I think everybody, who wants to use the list, may find info; in the
message's headers one may (and should) find even more info on how to
use, manage, configure the list.
IMHO store this in information body of a message, is useless payload.

Thankfully to mister Gooch, lkml faq was updated last August,
and every lkml's message doesn't point to a document, where first
word was: obsolete, any more. (maybe nobody saw that, but update with
"obsolete" was there)

=[OT/2]=

Also, i really want to know why switch from Usenet to LKML occurred.
Maybe there were problems with Usenet, but author of gmane.org, mr.
Lars Magne Ingebrigtsen, let me (and you) to use MLs as naturally as
news, described in rfc 977. It also helps us to achieve *goals* of news
system (rfc 977, 1.1). And, btw, he doesn't have sponsored hardware and
bandwidth form big IT.

If you will send me to archives without exact url or message-id,
i'll say: thank you very much (thinking about something other ;).

Really, web is a big PITA: searching archives of 90th, xmlandards and
web-clients, browsers (-fsck-, mkfs them all).

Developers are saying about "plain text", no MIME, < 80 wide lines
(other netiquette things), talking about SP@M in the LKML: all this
isn't natural for gmane.org-news, as far as i can see.

Consider SP@M, for example. I don't know what kind of it was in usenet
time, but now it's obviously @-based, and requiring valid e-mail address
is OK as for news, as for e-mail posts.

TIA.
____


  reply	other threads:[~2006-10-22  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 15:45 ANNOUNCEMENT: Real-time Linux users list created Theodore Ts'o
2006-10-22  7:56 ` Oleg Verych [this message]
2006-10-24  9:03   ` Mailing lists (again, was ANNOUNCEMENT: Real-time Linux users list created) Erik Mouw

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=slrnejm9d6.30t.olecom@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --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®