From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Cc: buildroot/buildroot
<reply+AAABTR2NR4RYNTYKRVDSQFWEJ3VJHEVBNHHIRRDM6M@reply.github.com>
Subject: Re: [Buildroot] [buildroot/buildroot] Repair libvncserver .mk file error (PR #141)
Date: Wed, 15 May 2024 17:01:20 +0200 [thread overview]
Message-ID: <87h6ezqfun.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <buildroot/buildroot/pull/141/issue_event/12796892545@github.com> (Thomas Petazzoni's message of "Mon, 13 May 2024 23:49:55 -0700")
>>>>> "Thomas" == Thomas Petazzoni <notifications@github.com> writes:
> Closed #141.
But the issue looks real, so I've posted a patch for it:
https://patchwork.ozlabs.org/project/buildroot/patch/20240515145903.363218-1-peter@korsgaard.com/
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
parent reply other threads:[~2024-05-15 15:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <buildroot/buildroot/pull/141/issue_event/12796892545@github.com>]
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=87h6ezqfun.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=reply+AAABTR2NR4RYNTYKRVDSQFWEJ3VJHEVBNHHIRRDM6M@reply.github.com \
--cc=thomas.petazzoni@bootlin.com \
/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).