From: zimoun <zimon.toutoune@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, 35169@debbugs.gnu.org
Subject: [bug#35169] [PATCH] gnu: Add urh.
Date: Thu, 07 Apr 2022 14:41:01 +0200 [thread overview]
Message-ID: <86czht2hia.fsf_-_@gmail.com> (raw)
In-Reply-To: <cu7ftq5xnd5.fsf@systemreboot.net> (Arun Isaac's message of "Fri, 26 Apr 2019 12:30:06 +0530")
Hi,
Looking at old patch submission, I hit this:
<http://issues.guix.gnu.org/issue/35169>
and I miss why it is not merged…
On Fri, 26 Apr 2019 at 12:30, Arun Isaac <arunisaac@systemreboot.net> wrote:
>>> + (synopsis "Driver for HackRF, a general purpose software
>>> defined radio")
>>> + (description "@code{hackrf} provides drivers for HackRF, a
>>> general purpose
>>> +software defined radio (SDR).")
>>
>> Drivers for… Linux? CUSE? Something else? (URH?)
>
> Actually, this package provides a library that uses libusb to interface
> with the HackRF software defined radio. Shall I rewrite the synopsis and
> description as follows, replacing "driver" with "library"? Or, should I
> say "userspace driver" instead of "library"?
>
> synopsis:
>
> Interface library for the HackRF software defined radio
>
> description:
>
> @code{hackrf} provides a library to interface with HackRF, a general
> purpose software defined radio.
…I mean, description and synopsis are important but they should not be a
blocker here. :-)
Arun, could you rebase and merge it?
Cheers,
simon
next prev parent reply other threads:[~2022-04-07 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 10:10 [bug#35169] [PATCH] gnu: Add urh Arun Isaac
2019-04-06 10:22 ` Danny Milosavljevic
2019-04-09 9:24 ` Arun Isaac
2019-04-16 10:31 ` Arun Isaac
2019-04-25 18:20 ` Arun Isaac
2019-04-25 18:45 ` Tobias Geerinckx-Rice
2019-04-26 7:00 ` Arun Isaac
2022-04-07 12:41 ` zimoun [this message]
2022-04-19 10:09 ` Arun Isaac
2022-04-29 12:45 ` bug#35169: " Guillaume Le Vaillant
2022-05-02 5:54 ` [bug#35169] " Arun Isaac
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=86czht2hia.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=35169@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.