Return-Path: X-Original-To: apmail-stdcxx-dev-archive@www.apache.org Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F63F44C1 for ; Mon, 27 Jun 2011 05:24:32 +0000 (UTC) Received: (qmail 38979 invoked by uid 500); 27 Jun 2011 05:24:31 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 38497 invoked by uid 500); 27 Jun 2011 05:24:17 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 38429 invoked by uid 99); 27 Jun 2011 05:24:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2011 05:24:08 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stefan.teleman@gmail.com designates 209.85.214.50 as permitted sender) Received: from [209.85.214.50] (HELO mail-bw0-f50.google.com) (209.85.214.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2011 05:24:01 +0000 Received: by bwb11 with SMTP id 11so1440695bwb.23 for ; Sun, 26 Jun 2011 22:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=GlgKLIduvm42wWyUpwB+vwAn2Y7lt2xptCPC/6kAVD4=; b=IDvD7F33Qm/PHYfGOLds7r5ftl3R2TWKYVuZx5tXsIuKWom0h951XHgvqsKGKCKDre tumBMODJr5uFIWNhQm3XY7vgS/5Pz75S2q77iHIdV0T5cvKh7MkV7vw0VoQjuZIQ3AoO rlgDTPxyp/tIMUaxPE4Z+lw+04oqEJmtzvR0c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sdam5Mx3tFMh0rhv21fFUlMe1/G5ah45gKcXP8k1ZHDDLa+t2HZlQ5MwUcCtoazuhf 7ZIkamvnqUnY9xlbwI2z5IhRGR94hiZ1X7K3fAZXDeWO393IqFtrnr6VfMsKhqIbXLwr S/i/ajY982F6Uz/e6tt9c2jzomowGIC23Fxuo= MIME-Version: 1.0 Received: by 10.204.9.197 with SMTP id m5mr2703912bkm.38.1309152221671; Sun, 26 Jun 2011 22:23:41 -0700 (PDT) Received: by 10.204.78.137 with HTTP; Sun, 26 Jun 2011 22:23:41 -0700 (PDT) In-Reply-To: <4E080551.404@pathscale.com> References: <4DFAE25E.9040703@pathscale.com> <4DFB7400.9080904@pathscale.com> <4E06B97C.10804@pathscale.com> <4E06CF4C.5080709@pathscale.com> <4E076B9F.4010801@pathscale.com> <4E080551.404@pathscale.com> Date: Mon, 27 Jun 2011 01:23:41 -0400 Message-ID: Subject: Re: STDCXX "fork" From: Stefan Teleman To: dev@stdcxx.apache.org, "stdcxx-dev@apache.org" Cc: =?UTF-8?Q?C=2E_Bergstr=C3=B6m?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 2011/6/27 "C. Bergstr=C3=B6m" : > Your false statements are annoying and unnecessary. I deeply regret that I am annoying you. > Please don't avoid the question as I'm trying to help review your changes= . > =C2=A0Either publicly or privately email which patch fixes which Perennia= l test. > =C2=A0(If in fact you've ran them at all) Quite frankly, I really don't need your help in reviewing my patches. They've already been reviewed. My current job description does not require me to help you run the Perennial validation tests, or to provide you with any information about the Perennial test results. As a matter of fact, I don't even have to provide you with patches at all. I am doing this as a courtesy: you stated that you wanted to look at the Solaris patches. You work for a compiler writer, and you stated you have a Perennial license. You should, therefore, be able to run the Perennial tests yourself. I stand by my previous statement: you have not validated the github fork of stdcxx against any validation test harness. Had you done so, several tests would/should have failed. Had you corrected the stdcxx code causing these failures (which you have not, I have verified that the violations are still there), several tests from the apache stdcxx test harness would have failed, and these tests would have required patches too. I do not see the necessary code changes, and I can tell all this by looking at the PathScale stdcxx fork code. --Stefan --=20 Stefan Teleman KDE e.V. stefan.teleman@gmail.com