From: "Martin Liška" <mliska@suse.cz>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
binutils@sourceware.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] PR lto/94249: Correct endianness detection with the __BYTE_ORDER macro
Date: Wed, 1 Apr 2020 12:01:30 +0200 [thread overview]
Message-ID: <2131cafa-703e-5f42-865b-e2f7f718dc83@suse.cz> (raw)
In-Reply-To: <alpine.LFD.2.21.2004011053210.3939520@eddie.linux-mips.org>
On 4/1/20 11:55 AM, Maciej W. Rozycki wrote:
> On Wed, 1 Apr 2020, Martin Liška wrote:
>
>>> OK to apply this hopefully obvious fix to GCC and then merge to binutils?
>>
>> I've just installed the patch.
>> @H.J. Can you please pull it to bintuils?
>
> Why didn't you use the commit as I published it
Because it didn't fit my script that takes changelog entries
and moves that to the corresponding ChangeLog files.
Next time, you will install the patch by your own.
> and also assumed
> authorship of my change? I feel insulted.
I removed myself from the ownership of the patch here:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=d3ee88fdb4e0f718aaba050a3eb7174b8934a29d
Martin
>
> Maciej
>
next prev parent reply other threads:[~2020-04-01 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200323103505.GF2156@tucnak>
[not found] ` <6313e487-6dbb-ac17-4160-4ac600af40be@suse.cz>
[not found] ` <7369b1aa-be0d-92cc-4f81-1612f101e2e8@suse.cz>
[not found] ` <CAFiYyc3yKQpWzh3Yzh7b40adi=gtFmYLeEZex_yCqYGSOdFcEw@mail.gmail.com>
[not found] ` <CAMe9rOqQf+3wO2rosK-jCNYEqc3e-OMP3NtVH0EX26aKGaFeBg@mail.gmail.com>
[not found] ` <3786da05-1530-38c5-e9e2-cd69418cd42a@suse.cz>
[not found] ` <CAMe9rOpFyGpzQwqsmz0ikZz3MhY4FsZYv_+jCNAHq0768vPw5Q@mail.gmail.com>
[not found] ` <5b27738a-9885-9906-0c93-888daf4a066f@suse.cz>
[not found] ` <20200324083109.GP2156@tucnak>
[not found] ` <e96704f3-9025-48af-f894-81401a5718a4@suse.cz>
[not found] ` <20200324091805.GQ2156@tucnak>
[not found] ` <b5a25c37-d29c-b636-04ef-eba959ad495b@suse.cz>
2020-03-31 13:27 ` Maciej W. Rozycki
2020-04-01 5:01 ` Hans-Peter Nilsson
2020-04-01 7:43 ` Martin Liška
2020-04-01 23:57 ` Hans-Peter Nilsson
2020-04-01 7:17 ` Richard Biener
2020-04-01 7:41 ` Martin Liška
2020-04-01 9:55 ` Maciej W. Rozycki
2020-04-01 10:01 ` Martin Liška [this message]
2020-04-01 15:59 ` Maciej W. Rozycki
2020-04-01 16:54 ` Martin Liška
2020-04-01 17:28 ` Maciej W. Rozycki
2020-04-01 10:04 ` Maciej W. Rozycki
2020-04-01 10:09 ` Martin Liška
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2131cafa-703e-5f42-865b-e2f7f718dc83@suse.cz \
--to=mliska@suse.cz \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=macro@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).