From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 109039 invoked by alias); 17 Apr 2018 02:35:03 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 109028 invoked by uid 89); 17 Apr 2018 02:35:02 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:674, H*UA:45.0, H*u:45.0, our X-HELO: mail-ot0-f176.google.com Received: from mail-ot0-f176.google.com (HELO mail-ot0-f176.google.com) (74.125.82.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 17 Apr 2018 02:35:01 +0000 Received: by mail-ot0-f176.google.com with SMTP id h8-v6so8695134otj.7 for ; Mon, 16 Apr 2018 19:35:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=7gclBtkR5fp5zwerFus8x7ASPESyaxN1Ymz2FvyMpEw=; b=o/ngcXmb+kUpSRGdl/vIcw8ofiq6ai/wtqBKtcbBgsxMU8RQTlQ9k0Zln1KTr7M+Nc eXwKONwXsjjs0nvMeMq0CXlSS3C8XrFZ+PhZvq5anHVFAnw/Fs0lOK+731YL1ufF+plR QrprBT2/SYZRIKoJODPWgqfhZVCnkFxGAyZ+AC+7bplVpuDuSRL/WZejbEuoG6PwX8sG +6VuFDtvFLL83h3Tmd3lE3kbar1gmXuAKdSHfbLmxBNbDVXhoe8bMbQQXxlX0FxtAjwz YH0He/a3TtFEzjWbMJ0/xNe0Ec62UgEV0vDiMLbLv2hKJGaorgEcX1yzxd3liVWhLrpy Jyhw== X-Gm-Message-State: ALQs6tBdtOxkl1mCsodu4FalUOufH6+2nPG3D5iS/4FDABTZMDBreTVR SuR5G7lkCxVNzIebjbi7QWRMZA== X-Google-Smtp-Source: AIpwx49LwJ4olv0pRrxLNBGzktJjEUXQ3RIJUU8tfcPJnHU3yJdE8D5q+m6AON4Tod+IfoTyD+ZwhA== X-Received: by 2002:a9d:3f75:: with SMTP id m108-v6mr155401otc.253.1523932499109; Mon, 16 Apr 2018 19:34:59 -0700 (PDT) Received: from localhost.localdomain (174-16-100-37.hlrn.qwest.net. [174.16.100.37]) by smtp.gmail.com with ESMTPSA id l25-v6sm5665581oii.24.2018.04.16.19.34.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Apr 2018 19:34:58 -0700 (PDT) To: David Malcolm , Gerald Pfeifer , GCC Mailing List From: Martin Sebor Subject: style of code examples in changes.html Message-ID: <5b1c9631-4dc1-8d44-0863-f2ddedda33e1@gmail.com> Date: Tue, 17 Apr 2018 10:39:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-04/txt/msg00099.txt.bz2 Hi David & Gerald, I noticed that the coding examples in the updates I committed to changes.html use a different formatting style than David's. I just copied mine from GCC 7 changes.html, and those I copied from David's for that version :) Should we make an effort to make them all look the same? FWIW, I didn't notice the difference until my changes published. I'm guessing that's because the style sheet the page uses isn't referenced from the original document and the reference is only added by Gerald's script. Is there a simple way to set things up so we can see our changes as they will appear when published? Thanks Martin