From: Jan Stary <hans@stare.cz>
To: "Måns Rullgård" <mans@mansr.com>
Cc: sox-devel@lists.sourceforge.net
Subject: release
Date: Mon, 13 Feb 2023 14:02:34 +0100 [thread overview]
Message-ID: <Y+o06ge2UcJRvu/L@www.stare.cz> (raw)
On Feb 07 14:20:42, mans@mansr.com wrote:
> > Also, last release was 8 years ago. Piling the patches
> > is starting to get cubersome when packaging downstream
> > - are there any plans for a release?
>
> I can slap a tag on the git repo and call it a day if that makes people
> happy.
Some would surely see a difference between that and a release,
but the diverging piles of patches downsteream would have
a common starting point .
> The process for creating the files comprising earlier releases
> is convoluted and probably broken in a million ways by now.
Yes, that is convoluted and broken; but I believe it can be
simplified: for example, there's no need to have a separate
macOS tarball or a precompiled binary, singling macOS out
among all the other unixes ...
Jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next reply other threads:[~2023-02-13 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 13:02 Jan Stary [this message]
2023-02-13 13:50 ` release Jan Stary
2023-02-13 20:12 ` release Jan Stary
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-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+o06ge2UcJRvu/L@www.stare.cz \
--to=sox-devel@lists.sourceforge.net \
--cc=mans@mansr.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.
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).