From: Juliusz Chroboczek <jch@irif.fr>
To: Dirk-Willem van Gulik <dirkx@webweaving.org>
Cc: galene@lists.galene.org
Subject: [Galene] Re: About UDP multiplexing
Date: Sun, 30 Mar 2025 23:22:57 +0200 [thread overview]
Message-ID: <87cydyz00e.wl-jch@irif.fr> (raw)
In-Reply-To: <D3433E01-82A8-4355-937A-7495528E706C@webweaving.org>
>> I'm not sure what's less confusing: using two mutually exclusive options,
>> or using a single option that's overloaded (currently, -udp-range does not
>> enable muxing, it merely restricts the range of ports used for un-muxed
>> sockets).
Changes this -- it's now
-udp-range port
or
-udp-range port1-port2
It still feels slightly off -- perhaps I should rename the option?
-- Juliusz
next prev parent reply other threads:[~2025-03-30 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 18:29 [Galene] " Juliusz Chroboczek
2025-03-22 20:32 ` [Galene] " Dirk-Willem van Gulik
2025-03-23 9:59 ` Juliusz Chroboczek
2025-03-23 11:42 ` Dirk-Willem van Gulik
2025-03-30 21:22 ` Juliusz Chroboczek [this message]
2025-03-31 4:29 ` Gabriel Pruvost-Kerneis
2025-03-31 11:46 ` Juliusz Chroboczek
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://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cydyz00e.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=dirkx@webweaving.org \
--cc=galene@lists.galene.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