From: Pedro Alves <pedro@palves.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] struct packed: Use gcc_struct on Windows
Date: Thu, 21 Jul 2022 19:57:00 +0100 [thread overview]
Message-ID: <4a32eaea-87a7-d2fa-6f40-89ea78bca086@palves.net> (raw)
In-Reply-To: <8335eumhjb.fsf@gnu.org>
On 2022-07-21 7:45 p.m., Eli Zaretskii wrote:
>> Cc: gdb-patches@sourceware.org
>> From: Pedro Alves <pedro@palves.net>
>> Date: Thu, 21 Jul 2022 19:30:23 +0100
>>
>>> If this is supposed to be based on our vigilance and manual prevention
>>> of exporting it, I think it's fragile and not very reliable. If we
>>> forget or miss something, we get a subtly broken build.
>>
>> I'm sorry, but this isn't making a lot of sense.
>
> You know, Pedro, it has become very hard to talk to you about almost
> anything here. You become annoyed almost from the second sentence I
> write, and your annoyance shows. It doesn't matter if the subject is
> some patch to documentation or something in the code, it is impossible
> for me to conduct any serious discussion without triggering your
> annoyance, with the resulting very unpleasant exchange.
>
I'm sorry that you feel that way. Maybe I should have chosen my words
a bit better above. I apologize if they came out too strong.
We do have our heated debates once in a while, but we always reach some conclusion,
and typically better than what either of us originally proposed, and I appreciate that.
From my side, I always do my best to explain my view. I have tried to do so in
this case as well.
It is really the case that we don't need to worry about ABI here. I can
try to explain better if there's a concrete problem you're seeing. (Problems
with some hypothetical external GDB API we can deal with if we ever get to
that.)
> I'm outta here.
>
I'm sorry to hear that.
next prev parent reply other threads:[~2022-07-21 18:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 15:21 [PATCH 0/3] struct packed and Windows ports (PR build/29373) Pedro Alves
2022-07-21 15:21 ` [PATCH 1/3] struct packed: Use gcc_struct on Windows Pedro Alves
2022-07-21 16:03 ` Eli Zaretskii
2022-07-21 17:05 ` Pedro Alves
2022-07-21 17:40 ` Eli Zaretskii
2022-07-21 18:15 ` Pedro Alves
2022-07-21 18:23 ` Eli Zaretskii
2022-07-21 18:30 ` Pedro Alves
2022-07-21 18:45 ` Eli Zaretskii
2022-07-21 18:57 ` Pedro Alves [this message]
2022-07-21 18:18 ` Pedro Alves
2022-07-21 18:28 ` Eli Zaretskii
2022-07-21 18:38 ` Pedro Alves
2022-07-21 15:21 ` [PATCH 2/3] struct packed: Unit tests and more operators Pedro Alves
2022-07-21 15:21 ` [PATCH 3/3] struct packed: Add fallback byte array implementation Pedro Alves
2022-07-25 14:58 ` [PATCH 0/3] struct packed and Windows ports (PR build/29373) Tom Tromey
2022-07-25 15:18 ` Pedro Alves
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=4a32eaea-87a7-d2fa-6f40-89ea78bca086@palves.net \
--to=pedro@palves.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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).