public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: linux-arm-kernel@lists.arm.linux.org.uk
Cc: Pavel Machek <pavel@ucw.cz>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Mailing List Etiquette
Date: Fri, 21 Aug 2009 10:06:54 +0200	[thread overview]
Message-ID: <200908211006.54879.marek.vasut@gmail.com> (raw)
In-Reply-To: <20090821072607.GA26983@atrey.karlin.mff.cuni.cz>

Dne Pá 21. srpna 2009 09:26:07 Pavel Machek napsal(a):
> > This message is sent to this mailing list once a week.
>
> Could we maybe reduce the frequency of this spam a little bit?
Hi!
Agreed
>
> >              1. Subscription requirements. [[24]rmk]
> >                 Recently, we have had to impose a restriction on the
> > mailing lists. You must be subscribed to the mailing list in order to
> > post messages to that mailing list. This is because of the UK Data
> > Protection laws. Only subscribe to these lists if you accept the legal
> > notice displayed on the relevant pages; by subscribing, you accept the
> > terms laid out in the legal notice. Answers will be copied to you.
>
> WTF? Did not we just have huge flamewar explaining this is untrue?

We wont have to care about any additional legal notices or whatever if the 
list moved to vger, would we ?
>
> >              6. Email attachments. [[36]rmk]
> >                 Please ensure that all attachments are plain text. There
> > is a limit of around 40KiB on the overall size of the message, so if you
> > want to send a large attachment, please upload it to a web site
>
> I thought limit was recently raised?
>
> >              10. Cross-posting between linux-arm* lists and other lists.
> > [[40]rmk] Please do not do this. Subscribers on other lists may not be
> > subscribed to the linux-arm lists, so when they try to reply to such a
> > message, they will receive a bounce. This is deemed by others to be rude
> > behaviour on the part of the person who originally cross-posted.
>
> Again, in recent flamewar you claimed crossposting is
> okay.

Crossposting doesn't seem to work much, I got rejects on LAK when I CCed it, 
but it might have been fixed already, it was a few weeks ago.

> 										Pavel

Cheers!
Marek

  parent reply	other threads:[~2009-08-21  8:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090819060004.GA23859@n2100.arm.linux.org.uk>
2009-08-21  7:26 ` Mailing List Etiquette Pavel Machek
2009-08-21  7:28   ` Pavel Machek
2009-08-21  8:06   ` Marek Vasut [this message]
2009-08-21  8:18   ` Russell King - ARM Linux
2009-08-21  8:30     ` Pavel Machek
2009-08-21  8:39       ` Russell King - ARM Linux
2009-08-21  8:55         ` David Miller
2009-08-21 14:54           ` Theodore Tso
2009-08-21 15:54             ` Bartlomiej Zolnierkiewicz
2009-08-21  9:05         ` Pavel Machek
2009-08-21 15:16           ` Eric Miao
2009-08-24  5:15             ` Miles Bader
2009-08-21  9:45     ` [PATCH] MAINTAINERS: ARM lists moved to vger.kernel.org Joe Perches
2009-08-21 11:54       ` Mikael Pettersson
2009-08-21 14:39         ` Joe Perches
2009-08-21 14:54           ` Martin Bogomolni

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=200908211006.54879.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=pavel@ucw.cz \
    /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