Github messages for voidlinux
 help / color / mirror / Atom feed
From: notthewave <notthewave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fprint: update to 1.90.x
Date: Sun, 27 Dec 2020 21:39:15 +0100	[thread overview]
Message-ID: <20201227203915.s5KI5iKEptYv9lGty-Xc8b5wI6rLpM5L5Dmb3ECbrMs@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: 654 bytes --]

New comment by notthewave on void-packages repository

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

Comment:
> Do you mind if I reopen the old PR (I'll write your name as the author) and have you test it?

No I don't, go ahead :smile: 

At first, I thought updating this would be a relatively trivial task, but looking at it now there are many things I'm not familiar with. E.g. Sub packages (when are they necessary?), etc. I'm very much  a beginner when it comes to `xbps-src` and packaging in general.
I'm fine with testing as the update includes some changes that fix an issue with my x230t (false positives)


  parent reply	other threads:[~2020-12-27 20:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 19:45 [PR PATCH] libfprint: update to 1.90.6 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
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 [this message]
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=20201227203915.s5KI5iKEptYv9lGty-Xc8b5wI6rLpM5L5Dmb3ECbrMs@z \
    --to=notthewave@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).