From: Jonathan Yong <10walls@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: realpath() patch to fix symlinks resolution for win32
Date: Mon, 6 Feb 2023 06:40:02 +0000 [thread overview]
Message-ID: <d74a11a5-7049-2183-cf89-7584a5ebe6e4@gmail.com> (raw)
In-Reply-To: <7c061f6c1c090362efbbcb9af9f6c758@autistici.org>
On 1/18/23 10:44, i.nixman--- via Gcc-patches wrote:
> hello again!
>
> the final version of the path for
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
>
> successfully bootstraped for x86_64-mingw32 and x86_64-linux.
>
> could anyone apply it please?
>
>
>
> best!
Looks good to me, please supply the appropriate changelog.
next prev parent reply other threads:[~2023-02-06 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 10:44 i.nixman
2023-02-06 6:40 ` Jonathan Yong [this message]
2023-02-11 6:32 ` Jonathan Yong
2023-02-11 7:28 ` i.nixman
2023-02-11 8:36 ` Jonathan Yong
2023-02-11 8:52 ` Gerald Pfeifer
2023-02-11 13:24 ` Jonathan Yong
2023-02-11 18:00 ` NightStrike
2023-02-11 21:14 ` Gerald Pfeifer
2023-02-13 12:03 ` Martin Liška
-- strict thread matches above, loose matches on Subject: below --
2023-01-26 17:51 i.nixman
2023-01-16 17:06 i.nixman
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=d74a11a5-7049-2183-cf89-7584a5ebe6e4@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.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).