From: "Raghav Gururajan" <rvgn@disroot.org>
To: Pronaip <pronaip@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Fingerprint GUI
Date: Fri, 17 May 2019 15:21:36 +0000 [thread overview]
Message-ID: <b6068cfbc2a2fa8464e6ad2e3757ae72@disroot.org> (raw)
In-Reply-To: <8JuS6mCyxHb4nKLYVGdUXyOGe-fkDWV8BYzQv7zK3ISfvOfKejS_QzNrhJfYSqXGNHOF3bonwSiZjzMuO8_cHe1bBhgp_6xnk1ZkVLyPuaA=@protonmail.com>
> The upek folder in the source I downloaded seems to contain compiled shared libraries in the lib
> and lib64 subfolders, so that's a bad sign.
I see.
next prev parent reply other threads:[~2019-05-17 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 11:52 Fingerprint GUI Raghav Gururajan
2019-05-17 14:19 ` Pronaip
2019-05-17 15:21 ` Raghav Gururajan [this message]
2019-05-18 9:12 ` Hartmut Goebel
2019-05-18 10:20 ` Tobias Geerinckx-Rice
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6068cfbc2a2fa8464e6ad2e3757ae72@disroot.org \
--to=rvgn@disroot.org \
--cc=guix-devel@gnu.org \
--cc=pronaip@protonmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).