From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Tmux crashes on copy
Date: Wed, 31 Jan 2024 18:36:51 +0100 [thread overview]
Message-ID: <878r45wgjw.fsf@> (raw)
In-Reply-To: <a910f721-6047-4162-a86b-61d4ec8f93ca@dronecode.org.uk> (Jon Turney via Cygwin's message of "Wed, 31 Jan 2024 13:39:18 +0000")
Jon Turney via Cygwin writes:
> If upstream really is making multiple releases called '6.4', which
> we're supposed to distinguish by some other means, then there aren't
> really any good answers...
There's only one official 6.4 release, but just about everyone packages
one of the roughly weekly snapshots inbetween releases (depending on
where you are looking they are also called beta versions), which are
named 6.4-yyyymmdd upstream. We can't have a "-" in the version number,
hence the suggestion to replace it with a "+".
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2024-01-31 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 12:30 David Stephenson
2024-01-18 7:37 ` Yasuhiro Kimura
2024-01-18 8:24 ` Takashi Yano
2024-01-21 20:09 ` Brian Inglis
2024-01-21 21:12 ` ASSI
2024-01-21 22:13 ` Brian Inglis
2024-01-31 13:39 ` Jon Turney
2024-01-31 15:56 ` marco atzeri
2024-01-31 17:36 ` ASSI [this message]
2024-01-31 20:45 ` ncurses version (was: Tmux crashes on copy) Brian Inglis
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=878r45wgjw.fsf@ \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).