Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58702 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98063 invoked from network); 6 Mar 2012 23:15:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Mar 2012 23:15:57 -0000 Authentication-Results: pb1.pair.com header.from=kris.craig@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=kris.craig@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender) X-PHP-List-Original-Sender: kris.craig@gmail.com X-Host-Fingerprint: 74.125.82.170 mail-we0-f170.google.com Received: from [74.125.82.170] ([74.125.82.170:50823] helo=mail-we0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E3/93-15021-CAA965F4 for ; Tue, 06 Mar 2012 18:15:57 -0500 Received: by werh12 with SMTP id h12so4082108wer.29 for ; Tue, 06 Mar 2012 15:15:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uKx0krZ5xFNzJ4fKD/Aos63qdfu2BCDPeQVHCQaD+p0=; b=rOI61Ky50xgwQLmRhaU0G0SjRcgzsa6WPR3Q5vhW83ATBlGgBXAD3R1zICTJy0NsAF Z6Yv1NS99v9FMsZlU95dk3Ujok9Wl1Hwd/LjDbqueYZ5+esEgWXneTtu56kB/WgNGYiX GGZa5aRSAPcMW2ovmeh+oJoG73klRzQObM9EWwJYKTuzadJ7frqVK81/imVXDYk5oNqv kr8b3IO+UJsLBYlxALg3KfUlGKM+mr+Ie35cn6hSmcdA1QkiVX31JUzKnIgq3McE/yE2 I9mp0CU3W6yz6gcG8v0Qqwz3F7gTv9EkLNC0ih5IUJnJKbT4VrKQZOLnB+6aInn9NSic LujQ== MIME-Version: 1.0 Received: by 10.180.24.7 with SMTP id q7mr17514092wif.11.1331075753505; Tue, 06 Mar 2012 15:15:53 -0800 (PST) Received: by 10.223.111.78 with HTTP; Tue, 6 Mar 2012 15:15:53 -0800 (PST) In-Reply-To: <4F5686C5.1030900@gmail.com> References: <4F54C488.6050209@lsces.co.uk> <4F555631.7090305@thelounge.net> <4F55F5E7.3080506@thelounge.net> <4F5686C5.1030900@gmail.com> Date: Tue, 6 Mar 2012 15:15:53 -0800 Message-ID: To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= Cc: Reindl Harald , internals@lists.php.net Content-Type: multipart/alternative; boundary=f46d043892ab74f25f04ba9b39ce Subject: Re: [PHP-DEV] ' > On 06/03/12 19:36, Kris Craig wrote: > > > > >> FIRST: > >> do NOT top post after get a reply below your text > >> or how do you imagine that anybody can follow a > >> thread where answers randomly before and after > >> the quotet text? > > Sorry. Sometimes I forget that there are some people out there who sti= ll > > use legacy non-threaded inboxes. I would recommend you consider > switching > > to Gmail or some other email client/service that supports threaded view= s. > > That will make it a lot easier for you to follow these threads. =3D) > Threaded MUAs won't help when fragments appear as > 3 > 1 > 2 > 4 > > In such cases, the people breaking the thread convention should > the very least remove all the other content. > And yes, his MUA does support threading. > > > I'll try this one last time: I don't know what the solution is. What I do know is that relying solely on, "people should...." is not a smart approach because people are going to break that convention regardless of whether they should or not. Yes, educating people is important, but that in and of itself isn't working. It doesn't work on any similar listserv I've subscribed to over the years. It just seems a bit naive to think that we can keep repeating the same pattern over and over and expect a different result. What I'm suggesting is that it would be to our benefit to think of a more sustainable approach. I'm not saying I know what that approach is, mind you. > > > > To clarify again, I was under the mistaken impression that > alias for short_open_tag. My argument was (and still is) against > > short_open_tag. I do see some use in this new echo alias for templatin= g > > purposes. > > > > --Kris > > ....And your point is? I initially thought this thread was saying that this alias had been removed and instead made to replace the short_open_tag. I stood corrected and we moved on. What does PHP 3 have to do with any of this? I think you've officially crossed the line from correcting somebody's error to beating a dead horse. ;P --Kris --f46d043892ab74f25f04ba9b39ce--