From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Upgrade Yaru++ to the new version 4.0
Date: Sun, 23 Aug 2020 22:14:30 +0200 [thread overview]
Message-ID: <20200823201430.Icf_la_Rr0YWYPYM4WjzMQ9MsxG53gW7atMW-agbkCg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24441@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
There's a merged pull request on the void-packages repository
Upgrade Yaru++ to the new version 4.0
https://github.com/void-linux/void-packages/pull/24441
Description:
Hello @pullmoll
In reference to #24125, in which I did something wrong.
But I unbderstood the squash, ran correctly the commands. I am not sure if I did something correct in this new PR.
next prev parent reply other threads:[~2020-08-23 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 20:11 [PR PATCH] " gusbemacbe
2020-08-23 20:14 ` pullmoll [this message]
2020-08-23 20:14 ` pullmoll
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=20200823201430.Icf_la_Rr0YWYPYM4WjzMQ9MsxG53gW7atMW-agbkCg@z \
--to=pullmoll@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).