From: "René via Sox-users" <sox-users@lists.sourceforge.net>
To: sox-users@lists.sourceforge.net
Cc: René <rene.erler@mailbox.org>
Subject: Re: Next release
Date: Tue, 11 May 2021 01:21:11 +0200 [thread overview]
Message-ID: <1f6ef538-054b-56c5-f0cd-c919ba2bbe33@mailbox.org> (raw)
In-Reply-To: <yw1xpmzbe3kf.fsf@mansr.com>
Am 03.04.2021 um 18:27 schrieb Måns Rullgård:
> René via Sox-users <sox-users@lists.sourceforge.net> writes:
>
>> Am 22.03.2021 um 12:32 schrieb Måns Rullgård:
>>> René via Sox-users <sox-users@lists.sourceforge.net> writes:
>>>
>>>> Hi all,
>>>>
>>>> Does anybody know if or when there is a new sox release scheduled? :)
>>> No, nobody knows.
>> How come? Please, excuse my ignorance.
> There will be a release when I get round to it.
Alright. What’s the best way to stay in the loop about a new release? Is
there usually gonna be a post in the mailing list here?
>
>>>> I'd love to get my hands on a version that has some of the bug fixes from
>>>> 2020 included.
>>>>
>>>> Any info is highly appreciated.
>>> You could build it yourself.
>> Thx. So current code snapshots are considered to be fully
>> functional/(stable)?
> The master branch from git is the best version.
Ok, thanks.
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2021-05-10 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 17:01 Next release René via Sox-users
2021-03-22 11:32 ` Måns Rullgård
2021-04-02 12:47 ` René via Sox-users
2021-04-03 16:27 ` Måns Rullgård
2021-05-10 15:57 ` Bez Lukru via Sox-users
2021-05-10 23:21 ` René via Sox-users [this message]
2021-05-11 0:01 ` John Dyson via Sox-users
2021-05-11 12:32 ` Jeff Learman
2021-05-11 12:45 ` Måns Rullgård
2021-05-11 23:29 ` René via Sox-users
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f6ef538-054b-56c5-f0cd-c919ba2bbe33@mailbox.org \
--to=sox-users@lists.sourceforge.net \
--cc=rene.erler@mailbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
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).