From: NightStrike <nightstrike@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jonathan Yong <10walls@gmail.com>,
i.nixman@autistici.org, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: realpath() patch to fix symlinks resolution for win32
Date: Sat, 11 Feb 2023 13:00:38 -0500 [thread overview]
Message-ID: <CAF1jjLsqHtdg7hZipBAaWMvgWGwV8PPJyN_iyaLDV4J1ippDgw@mail.gmail.com> (raw)
In-Reply-To: <c7838d50-fd9f-6385-7238-820b3b7b14bc@pfeifer.com>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
On Sat, Feb 11, 2023 at 3:52 AM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Sat, 11 Feb 2023, Jonathan Yong via Gcc-patches wrote:
> >> could you please close the corresponding BR too?:
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
> > I can't close it, but I put a note that it has been committed.
>
> I closed the report.
>
> Gerald
I would have expected the PR to have been automatically updated based on
the commit email. Any idea why that didn't happen? Not to change the state
to closed, but to add the commit information as a reply.
next prev parent reply other threads:[~2023-02-11 18:00 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
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 [this message]
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=CAF1jjLsqHtdg7hZipBAaWMvgWGwV8PPJyN_iyaLDV4J1ippDgw@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=i.nixman@autistici.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).