From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by sourceware.org (Postfix) with ESMTPS id 76C3A385BF92 for ; Wed, 1 Apr 2020 10:09:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 76C3A385BF92 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mliska@suse.cz X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 903F1ADBE; Wed, 1 Apr 2020 10:09:49 +0000 (UTC) Subject: Re: [PATCH] PR lto/94249: Correct endianness detection with the __BYTE_ORDER macro To: "Maciej W. Rozycki" Cc: Jakub Jelinek , GCC Patches , binutils@sourceware.org, "H.J. Lu" References: <20200323103505.GF2156@tucnak> <6313e487-6dbb-ac17-4160-4ac600af40be@suse.cz> <7369b1aa-be0d-92cc-4f81-1612f101e2e8@suse.cz> <3786da05-1530-38c5-e9e2-cd69418cd42a@suse.cz> <5b27738a-9885-9906-0c93-888daf4a066f@suse.cz> <20200324083109.GP2156@tucnak> <20200324091805.GQ2156@tucnak> <58a785c1-08fc-a491-e19d-2b42e0a9817b@suse.cz> From: =?UTF-8?Q?Martin_Li=c5=a1ka?= Message-ID: Date: Wed, 1 Apr 2020 12:09:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-18.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 10:09:51 -0000 On 4/1/20 12:04 PM, Maciej W. Rozycki wrote: > On Wed, 1 Apr 2020, Martin Liška wrote: > >>> NB if posting as an attachment please try matching the message subject >>> with the change heading as otherwise it takes a lot of effort to track the >>> patch submission corresponding to a given commit. >> >> I see your point, but note that sometimes a direction of a patch changes >> during >> the mailing list discussion. And so that we end up with a commit message that >> has a different name. > > What's the problem with changing the message subject at the point the > final change is posted, just as I did with the change I submitted (where > you chose to actually ignore what I posted and gratuitously changed the > commit heading from one I used anyway)? Yes, that was a mistake, sorry for that. Martin > > Maciej >