From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libmtp: update to 1.1.19, use plugdev group for r/w access to mtp devices.
Date: Sun, 10 Apr 2022 22:42:21 +0200 [thread overview]
Message-ID: <20220410204221.MvgiSXnkDFEvjJRiwqyTw3jVQiJSmPmarsmX0Xknfik@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34757@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/34757#issuecomment-1094365227
Comment:
@q66 since you merged #36238 (plugdev standard group), could you please take a look at this?
The update itself is uninteresting, but I changed the template so that libmtp uses `plugdev` group for r/w permission to mtp devices (before this change, there was no way to use libmtp without root).
I've been using this without any trouble (I use it via `gmtp` to upload music to my garmin watch).
next prev parent reply other threads:[~2022-04-10 20:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 21:42 [PR PATCH] libmtp: update to 1.1.19 tornaria
2022-01-04 8:01 ` [PR REVIEW] " ericonr
2022-01-05 1:15 ` tornaria
2022-01-20 13:21 ` tornaria
2022-02-25 21:55 ` Piraty
2022-02-25 21:57 ` Piraty
2022-02-25 22:03 ` tornaria
2022-02-25 22:15 ` tornaria
2022-02-25 23:08 ` Piraty
2022-02-26 0:32 ` Piraty
2022-02-26 13:35 ` tornaria
2022-02-26 21:58 ` Piraty
2022-02-27 17:38 ` tornaria
2022-03-19 23:07 ` [PR PATCH] [Updated] " tornaria
2022-03-19 23:10 ` [PR REVIEW] " tornaria
2022-03-19 23:12 ` tornaria
2022-04-06 22:53 ` 0x5c
2022-04-10 20:42 ` tornaria [this message]
2022-04-10 23:39 ` [PR PATCH] [Merged]: libmtp: update to 1.1.19, use plugdev group for r/w access to mtp devices q66
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=20220410204221.MvgiSXnkDFEvjJRiwqyTw3jVQiJSmPmarsmX0Xknfik@z \
--to=tornaria@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).