From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net
Subject: upstream and bugfixes
Date: Tue, 7 Feb 2023 14:31:56 +0100 [thread overview]
Message-ID: <Y+JSzAqzs2A3mOfe@www.stare.cz> (raw)
Hi Mans,
just to clear it up for myself:
https://sourceforge.net/p/sox/code/ci/master/tree/
is still the ultimate upstream, right?
For reference: there is also
https://github.com/cbagwell/sox (last commit 2015, 4 issues, 2 PRs)
https://github.com/mansr/sox (forked, last 2017, 1PR, no issue tracker)
(and a bunch of nobody's forks of these of course, such as mine).
These can be ignored when packaging downstream, right?
Are the commits in your GH fork included in the SF git?
What is currently the right way to report bugs and propose fixes?
Are diffs to this devel list the preffered way?
The SF issues seem to be untouched for years.
Last commit to the SF git is May 2021; where should current fixes
such as https://marc.info/?l=oss-security&m=167546008232629&w=2 be sent?
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?
Jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next reply other threads:[~2023-02-07 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 13:31 Jan Stary [this message]
2023-02-07 14:20 ` upstream and bugfixes Måns Rullgård
2023-02-07 16:27 ` Jan Stary
2023-02-13 9:47 ` Jan Stary
2023-02-13 12:54 ` 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+JSzAqzs2A3mOfe@www.stare.cz \
--to=sox-devel@lists.sourceforge.net \
/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).