From: Pedro Alves <pedro@palves.net>
To: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Down with SO_NAME_MAX_PATH_SIZE and windows_make_so spring cleaning
Date: Fri, 22 Mar 2024 19:49:23 +0000 [thread overview]
Message-ID: <63920eab-87c1-4f43-83fd-77294e6283fa@palves.net> (raw)
In-Reply-To: <855f966e-878a-431d-acc9-0515cd6def4d@FreeBSD.org>
On 2024-03-22 19:37, John Baldwin wrote:
> On 3/22/24 12:04 PM, Pedro Alves wrote:
>> The commit subjects below say it all.
>>
>> Pedro Alves (4):
>> Remove SO_NAME_MAX_PATH_SIZE limit from core solib code
>> Simplify windows-nat.c:windows_make_so #ifdefery
>> windows-nat: Remove SO_NAME_MAX_PATH_SIZE limit
>> windows-nat: Use gdb_realpath
>>
>> gdb/solib.c | 2 --
>> gdb/windows-nat.c | 42 ++++++++++++++++++++++++------------------
>> 2 files changed, 24 insertions(+), 20 deletions(-)
>>
>>
>> base-commit: 319719bb2921e978738acd408e6b16dabf0e7f5e
>
> These all look good to me.
>
> Approved-By: John Baldwin <jhb@FreeBSD.org>
>
Thanks John. I added your tag and merged this.
prev parent reply other threads:[~2024-03-22 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 19:04 Pedro Alves
2024-03-22 19:04 ` [PATCH 1/4] Remove SO_NAME_MAX_PATH_SIZE limit from core solib code Pedro Alves
2024-03-22 19:04 ` [PATCH 2/4] Simplify windows-nat.c:windows_make_so #ifdefery Pedro Alves
2024-03-22 19:04 ` [PATCH 3/4] windows-nat: Remove SO_NAME_MAX_PATH_SIZE limit Pedro Alves
2024-03-22 19:04 ` [PATCH 4/4] windows-nat: Use gdb_realpath Pedro Alves
2024-03-22 19:37 ` [PATCH 0/4] Down with SO_NAME_MAX_PATH_SIZE and windows_make_so spring cleaning John Baldwin
2024-03-22 19:49 ` Pedro Alves [this message]
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=63920eab-87c1-4f43-83fd-77294e6283fa@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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