From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
"Geoffrey McRae" <geoff@hostfission.com>,
"José Pekkarinen" <koalinux@gmail.com>
Subject: Re: [PATCH v2] Autoconnect jack ports by default
Date: Thu, 04 Mar 2021 12:24:44 +0100 [thread overview]
Message-ID: <1992957.OTMv4WkKIP@silver> (raw)
In-Reply-To: <20210303071306.h6nmeoau447w4j4b@sirius.home.kraxel.org>
On Mittwoch, 3. März 2021 08:13:06 CET Gerd Hoffmann wrote:
> Hi,
>
> > JACK clients with consumer purpose often auto connect to system ports by
> > default because their users mostly use JACK just as a consumer desktop
> > sound server. And I assume this applies to José as well.
>
> Hmm, ok. I'd suggest to simply change the default for connect-ports
> then, that'll allow the user to easily change the behavior by setting
> connect-ports to something else (including the empty string to disable
> autoconnect).
>
> take care,
> Gerd
Geoffrey, any chance to make you happy as well? E.g. either reserving "none"
as special value for "connect-ports" or an additional CL argument
"no-connect-ports" to make it appear less hackish?
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2021-03-04 11:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 19:19 [PATCH v2] Autoconnect jack ports by default José Pekkarinen
2021-02-24 19:39 ` Christian Schoenebeck
2021-02-24 22:04 ` Geoffrey McRae
2021-02-24 22:33 ` Christian Schoenebeck
2021-02-24 22:38 ` Geoffrey McRae
2021-02-25 8:31 ` José Ramón Muñoz Pekkarinen
2021-02-25 8:48 ` Gerd Hoffmann
2021-02-26 11:40 ` Christian Schoenebeck
2021-03-03 7:13 ` Gerd Hoffmann
2021-03-04 11:24 ` Christian Schoenebeck [this message]
2021-03-04 11:56 ` Daniel P. Berrangé
2021-03-04 13:12 ` Gerd Hoffmann
2021-03-04 13:53 ` Daniel P. Berrangé
2021-03-04 14:12 ` Gerd Hoffmann
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=1992957.OTMv4WkKIP@silver \
--to=qemu_oss@crudebyte.com \
--cc=geoff@hostfission.com \
--cc=koalinux@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).