- Simplified git describe to version string parsing.
- Making up the unthinkable (aka. v1.0.0) (2)
- Making up the unthinkable (aka. v1.0.0)
- Prepping up the unthinkable (aka. v1.0.0)
- Prepping the unthinkable (aka. v1.0.0-rc2)
- Prepping the unthinkable (aka. v1.0.0-rc2)
- Prepping the unthinkable (aka. v1.0.0-rc2)
Updated rpm.spec to partial openSUSE standards.
- Prepping next release candidate (aka. v1.0.0-rc2) (Qt >= 6.7)
- Prepping A Spring'24 Release Candidate (aka. v1.0.0-rc1)
- Prepping the unthinkable (aka. v1.0.0-rc1)
- Prepping the unthinkable (aka. v1.0.0-rc1)
- Early preppings for the unthinkable...
- A Winter'24 Release (v0.9.12)
- A Winter'24 Release (v0.9.12)
- Preppings to an end-of-summer'23 release...
- Rephrased the new year copyright project line.
- Just added a new-line to about-box text for padding.
- Updated copyright headers into the New Year. (final)
- Updated copyright headers into the New Year. (bis)
- Updated copyright headers into the New Year (2024).
- Replace foreach() macros with C++11 for() constructs. (REGRESSION)
- Micro-management on buil-depends order to rpm.spec
- Replaced foreach() macros with C++ for() constructs.
- Cleanup all scalable icons (SVG)
- Bumping up to Qt6.6 (static) where needed... (rpm; deb)
- Bumping up to Qt6.6 (static) where needed... (bis)
- Bumping up to Qt6.6 (static) where needed...
- Fixing unique/single instance support (Qt >= 6.6)
- Fix some ctor. uninitialized vars.
- Add Unique/Single instance support. (EXPERIMENTAL)
- Bumping into next development cycle (Qt >= 6.6)
- Update rpm.spec to pkgconfig(alsa)
- Preppings to an end-of-summer'23 release...
- Updated/modernized debian control files.
- Updated to new qt*6.5-static package names (debian, rpm)
- Preppings to next development cycle (Qt >= 6.6)
- Early prepping for the next Spring'23 release.
- Early prepping for the next Spring'23 release. (bis
- Early prepping for the next Spring'23 release.
- Updated debian build-deps control (+qt6-svg-dev)
- Reduced watchdog check to 1min. (was 3min.)
all repos are mirrored; here SF is fine but GH is kinda more popular :)
Thanks Rui - which repo is the main one to request against? I guess the one here at sourceforge.
MR == Merge Request == Pull Request you should know by now that a git pull is a git fetch followed by a git merge, don't you?
MR == Merge Request == Pull Request you should know that a git pull == git fetch + git merge, don't you?
"MR"? I couldn't figure out where (of the many web appearances) to post a patch / pull request. I have been using git for some time so tend to branch, fix, PR but wasn't sure of your contribution mechanism.
good catch... your suggestion is now in [7e8e2f] next time propose a MR? thanks
- Fixed lost or out of order messages on JACK-MIDI client.
Lost or out of order messages to jack client
- Prepping into the next development cycle (with Qt >= 6.5).
- Prepping into the next development cycle (with Qt >= 6.5).
- Late preppings for the Early-Spring'23 release.
Windows version
Run multiple times in one box?
IPv6 support