From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hackrf: fix udev rules directory
Date: Sun, 02 Oct 2022 23:34:46 +0200 [thread overview]
Message-ID: <20221002213446.1hcdHWXS8XCuJpgvBhk5YXc06VjroKn5Ap8pZhBsFs4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39633@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
New comment by Piraty on void-packages repository
https://github.com/void-linux/void-packages/pull/39633#issuecomment-1264738106
Comment:
before
```
xbps-query -Rf libhackrf | grep udev
/usr/lib/udev/rules.d/53-hackrf.rules
xbps-query -Rf hackrf | grep udev
```
after
```
fd -t f rules masterdir/destdir
masterdir/destdir/hackrf-2021.03.1/usr/lib/udev/rules.d/53-hackrf.rules
```
next prev parent reply other threads:[~2022-10-02 21:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 20:21 [PR PATCH] " motorto
2022-10-02 20:25 ` [PR PATCH] [Updated] " motorto
2022-10-02 20:36 ` motorto
2022-10-02 21:32 ` Piraty
2022-10-02 21:34 ` Piraty [this message]
2022-10-02 21:56 ` paper42
2022-10-03 5:57 ` motorto
2022-10-03 6:00 ` [PR PATCH] [Updated] " motorto
2022-10-03 12:33 ` classabbyamp
2022-10-03 15:40 ` Piraty
2022-10-04 9:40 ` motorto
2022-10-04 9:40 ` [PR PATCH] [Updated] " motorto
2022-10-04 9:42 ` motorto
2022-10-04 11:02 ` motorto
2022-10-04 11:08 ` Piraty
2022-10-04 11:14 ` [PR PATCH] [Updated] " motorto
2022-10-04 17:32 ` classabbyamp
2022-10-04 17:33 ` classabbyamp
2022-10-04 19:37 ` [PR PATCH] [Updated] " motorto
2022-10-04 19:41 ` motorto
2022-10-04 19:46 ` motorto
2022-10-04 19:50 ` [PR PATCH] [Updated] " motorto
2022-10-04 20:46 ` classabbyamp
2022-10-04 20:49 ` [PR PATCH] [Updated] " motorto
2022-10-04 20:56 ` motorto
2022-10-04 21:01 ` [PR PATCH] [Merged]: " classabbyamp
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=20221002213446.1hcdHWXS8XCuJpgvBhk5YXc06VjroKn5Ap8pZhBsFs4@z \
--to=piraty@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).