From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libcppunit: update to 1.15.1.
Date: Mon, 23 Nov 2020 10:48:32 +0100 [thread overview]
Message-ID: <20201123094832.Z9yrwPWhIeVx1wIvue568SQ0VluaLs2RhUgWAp_sZhY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26513@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
New comment by mobinmob on void-packages repository
https://github.com/void-linux/void-packages/pull/26513#issuecomment-732047815
Comment:
Thank you for the review, but I cannot test all the revbumps locally and I seriously doubt the c-i can handle them on a PR. So, I am closing it...
prev parent reply other threads:[~2020-11-23 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 22:26 [PR PATCH] " mobinmob
2020-11-19 23:04 ` [PR PATCH] [Updated] " mobinmob
2020-11-23 3:40 ` ericonr
2020-11-23 9:47 ` mobinmob
2020-11-23 9:47 ` [PR PATCH] [Closed]: " mobinmob
2020-11-23 9:48 ` mobinmob [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=20201123094832.Z9yrwPWhIeVx1wIvue568SQ0VluaLs2RhUgWAp_sZhY@z \
--to=mobinmob@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).