From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272284AbTGYUKI (ORCPT ); Fri, 25 Jul 2003 16:10:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272285AbTGYUKH (ORCPT ); Fri, 25 Jul 2003 16:10:07 -0400 Received: from 81-2-122-30.bradfords.org.uk ([81.2.122.30]:43138 "EHLO 81-2-122-30.bradfords.org.uk") by vger.kernel.org with ESMTP id S272284AbTGYUKE (ORCPT ); Fri, 25 Jul 2003 16:10:04 -0400 Date: Fri, 25 Jul 2003 21:35:20 +0100 From: John Bradford Message-Id: <200307252035.h6PKZKts001817@81-2-122-30.bradfords.org.uk> To: lgcdutra@terra.com.br, linux-kernel@vger.kernel.org Subject: Re: Posting format Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > Can we all, please, at least do things like not repeatedly quoting the > > list's four-line signature, and not quoting things like .config files? > > One more: don't answer to people directly, only thru the list. > It is quite annoying to receive the same message twice, especially if > on a flamewar... > > Actually I was quite surprised to learn these rules aren't > followed here. No, that is not the etiquette on this list, please _don't_ break the CC list when replying - the FAQ particularly mentions this in section 5.3. Breaking the CC list is very likely to reduce your chances of a reply from a lot of developers. The main reason for this is that as LKML is a high volume mailing list, a lot of developers will simply delete list mail unread if they are busy, assuming that anything that the poster really wanted them to see would be mailed directly to them, as well as to the list. Receiving the same message twice is generally a non-issue - the list is high-volume anyway, so the odd duplicate message won't use up that much extra bandwidth. John.