From: Wolfgang Denk Date: Mon, 01 Jun 2009 22:51:02 +0200 Subject: [U-Boot] REJECT: Too many recipients to the message In-Reply-To: <20090601203258.GG8553@email.mot.com> References: <20090601175808.BD41D832E416@gemini.denx.de> <4A242071.1010806@freescale.com> <20090601200012.D8869832E416@gemini.denx.de> <20090601203258.GG8553@email.mot.com> Message-ID: <20090601205102.A6047832E416@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear T Ziomek, In message <20090601203258.GG8553@email.mot.com> you wrote: > > Yes, but how one's MUA / mail client handles them may *not* be identi- > cal. > > Quite a few people configure their MUA to prioritize messages based on > whether they are on the To: list, CC:, BCC:, or none of the above (i.e. > by list membership). I read this as a pro for long cc: lists. > > What is the difference whether you receive one or two identical copies > > of a message? > > It's a hassle and distraction to deal with duplicates. This however is a clear con, isn't it? > > > How about reconfiguring the list software instead? > > > > I see no reason for that yet. > > +1 for not restricting the # of addressees absent a reason other than > "some of them are often redundant". We neever before had any such problems. Currently these are caused because some messages have 5 (or more) samsung.com addresses listed on Cc:; for example, "[PATCH] The omap3 L2 cache enable/disable function to omap3 dependent code" has 6 such addresses on Cc: I doubt that this is really necessary. In this specific case, a company-internal distribution list would probably be more appropriate. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de A Vulcan can no sooner be disloyal than he can exist without breathing. -- Kirk, "The Menagerie", stardate 3012.4