From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lkml subject line
Date: Wed, 14 Feb 2001 11:31:07 +0200 [thread overview]
Message-ID: <20010214113107.W15688@mea-ext.zmailer.org> (raw)
In-Reply-To: <20010212133324.B15688@mea-ext.zmailer.org> <7vh2Hebmw-B@khms.westfalen.de> <3A885DFF.824AC093@inet.com> <20010214031125.B30531@cadcamlab.org>
In-Reply-To: <20010214031125.B30531@cadcamlab.org>; from peter@cadcamlab.org on Wed, Feb 14, 2001 at 03:11:25AM -0600
On Wed, Feb 14, 2001 at 03:11:25AM -0600, Peter Samuelson wrote:
> [Eli Carter]
> > Have you looked at the headers in an LK email?
> >
> > Sender: linux-kernel-owner@vger.kernel.org
> > X-Mailing-List: linux-kernel@vger.kernel.org
> > ^^^^^^^^^^^^^^ Should provide that List-Id you want.
>
> You missed the point. Certainly there are ways to identify LK mail.
> Kai is saying that since 'List-Id:' is an IETF proposed standard,
> Majordomo ought to use it.
There is no STANDARDS TRACK RFC saying anything about List-Id:.
There are only some individual's submission for a draft about it.
It is also way overdue to expire (Expires September 23, 1999), and
it has not been updated, nor advanced towards RFC.
There are issues where me and DaveM are as obstinate as Linus,
inserting lots of junky headers and munging others (e.g. Subject:)
is a big no-no. You can hash the issue all you want, but you
can't convince me and DaveM.
That X-Mailing-List: is actually a LOOP detection measure.
http://vger.kernel.org/lkml/#s3-9
I do have some plans which will change things at VGER, but those
details are not ready for publishing yet.
> Peter
/Matti Aarnio
next prev parent reply other threads:[~2001-02-14 9:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 11:20 Guennadi Liakhovetski
2001-02-12 11:28 ` David Woodhouse
2001-02-12 11:33 ` Matti Aarnio
2001-02-12 15:13 ` Guest section DW
2001-02-12 15:19 ` David Woodhouse
2001-02-12 15:25 ` Mike Harrold
2001-02-12 15:29 ` David Woodhouse
2001-02-12 18:45 ` Mohammad A. Haque
2001-02-12 19:05 ` Matthew D. Pitts
2001-02-12 19:29 ` Mohammad A. Haque
2001-02-12 21:40 ` Gerhard Mack
2001-02-13 8:56 ` Mike A. Harris
2001-02-13 8:54 ` Mike A. Harris
2001-02-13 11:16 ` Alan Cox
2001-02-13 11:29 ` Mike A. Harris
2001-02-13 13:22 ` Mohammad A. Haque
2001-02-12 18:58 ` Timur Tabi
2001-02-12 20:02 ` J . A . Magallon
2001-02-13 8:46 ` Mike A. Harris
2001-02-13 10:12 ` Sven Koch
2001-02-13 10:30 ` Mike A. Harris
2001-02-12 16:48 ` Bruce Harada
2001-02-12 16:56 ` Mike Harrold
2001-02-12 17:07 ` Lars Marowsky-Bree
2001-02-12 17:17 ` [LK] " Mike Harrold
2001-02-12 21:24 ` Gerhard Mack
2001-02-13 8:53 ` Mike A. Harris
2001-02-13 12:40 ` Mike Harrold
2001-02-13 17:15 ` Timur Tabi
2001-02-13 18:08 ` Mike A. Harris
2001-02-15 9:38 ` Paul Jakma
2001-02-15 14:53 ` Mike Harrold
2001-02-18 1:55 ` Chipzz
2001-02-13 8:49 ` Mike A. Harris
2001-02-12 17:11 ` Bruce Harada
2001-02-12 19:26 ` Guest section DW
2001-02-12 20:39 ` Kai Henningsen
2001-02-12 22:04 ` Eli Carter
2001-02-14 9:11 ` Peter Samuelson
2001-02-14 9:31 ` Matti Aarnio [this message]
[not found] ` <200102140950.KAA10814@cave.bitwizard.nl>
2001-02-14 10:50 ` Linux-kernel traffic statistics Matti Aarnio
2001-02-12 22:23 ` lkml subject line Mohammad A. Haque
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=20010214113107.W15688@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cadcamlab.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®