Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libfprint: update to 1.90.6
Date: Sun, 20 Dec 2020 22:42:16 +0100	[thread overview]
Message-ID: <20201220214216.mx4SN3Z_4IAxoLiDo5eR1IVXGH14_grGlIF0v_9n_P8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27311@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 242 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/27311#issuecomment-748674723

Comment:
I won't restart CI, since I assume you're going to push new things. It should be working now, though.

  parent reply	other threads:[~2020-12-20 21:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 19:45 [PR PATCH] " notthewave
2020-12-20 19:53 ` ericonr
2020-12-20 20:01 ` notthewave
2020-12-20 20:43 ` [PR PATCH] [Updated] " notthewave
2020-12-20 20:54 ` notthewave
2020-12-20 20:55 ` notthewave
2020-12-20 20:58 ` notthewave
2020-12-20 21:02 ` ericonr
2020-12-20 21:04 ` notthewave
2020-12-20 21:36 ` notthewave
2020-12-20 21:42 ` ericonr [this message]
2020-12-21  0:37 ` sgn
2020-12-21  6:07 ` notthewave
2020-12-21  6:11 ` ericonr
2020-12-21  6:12 ` ericonr
2020-12-21 17:52 ` fprint: update to 1.90.x notthewave
2020-12-21 17:55 ` notthewave
2020-12-21 18:01 ` ericonr
2020-12-21 18:01 ` ericonr
2020-12-21 18:03 ` notthewave
2020-12-21 18:04 ` notthewave
2020-12-21 18:06 ` notthewave
2020-12-21 18:11 ` notthewave
2020-12-21 18:12 ` notthewave
2020-12-21 18:13 ` notthewave
2020-12-21 18:57 ` notthewave
2020-12-21 20:50 ` notthewave
2020-12-21 21:02 ` [PR PATCH] [Updated] " notthewave
2020-12-22 12:37 ` sgn
2020-12-26 14:40 ` notthewave
2020-12-27  2:02 ` sgn
2020-12-27 20:39 ` notthewave
2021-01-13 16:06 ` sgn
2021-01-13 16:06 ` [PR PATCH] [Closed]: " sgn

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=20201220214216.mx4SN3Z_4IAxoLiDo5eR1IVXGH14_grGlIF0v_9n_P8@z \
    --to=ericonr@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).