Activity for Boris Pek
-
Boris Pek committed [8cf100]
Fix build with -Werror
-
Stable release 0.8.1
-
Fix some cppcheck notes
-
Fix encoding in header file
-
Merge branch 'windows-build'
-
Attempt to fix cross-compilation for MS Windows.
-
Update .gitignore
-
Thanks for the program!
-
Not a bug + looks as an ad.
-
Add missed include
-
Fix results file saving
-
Fix results file saving
-
Accepted. Thanks! 80436ee16923793e0a55bd0bb4d7a16bc5558506
-
Update ChangeLog
-
Fix saving results to *.qpx files
-
Fix Pioneer QuietMode operation
-
https://github.com/tehnick/yagf-debian/blob/master/debian/yagf.1
-
spelling errors
-
Fix: http://svnweb.mageia.org/packages/cauldron/yagf/current/SOURCES/yagf-0.9.5-do-not-crash-when-specific-aspell-dictionary-is-not-found.patch?revision=1555054&view=co
-
Stable release 0.8.0
-
Update website URL
-
Fix TODO
-
Fix FTBFS with libpng >= 1.4
-
Fix FTBFS on Debian GNU/kFreeBSD
-
Use compiler options from build environment
-
Fix desktop file
-
Do not use /usr/lib64/qpxtool for plugins
-
Update ChangeLog
-
Update man pages
-
Fix spelling errors
-
Fix checking of libpng in configuration script
-
Fix declarations of unsigned char in wr_mode
-
Port application to Qt 5.x
-
Add .gitignore
-
Fix spelling errors
-
Add support of Debian GNU/Hurd
-
Update README.
-
Update license notices
-
Mercurial is extremely inconvenient and intransparent software. Please merge or reject this MR, so I will be able to propose other changes. Or do you reject changes from exterior developers at all? This would explain the amount of DC++ forks...
-
Ping?
-
Ping?
-
Please merge or reject this MR.
-
unless lawyers who would know better can confirm the website-address version also works for GPL 2? :) Why do you need a lawyers opinion if article at page https://www.gnu.org/licenses/gpl-howto.en.html exlicitly say: To use a different set of GPL versions, you would modify the end of the first long paragraph. For instance, to license under version 2 or later, you would replace “3” with “2”.
-
And I didn't even mention that: Paper correspondence for such issues in 2019 is absolute nonsense. Other projects under GPLv2 license already use proposed above license notices during long time and I have not heard about any issues with this.
-
And I didn't even mention that: Paper correspondence for such issues in 2019 is absolute nonsense. Other projects under GPLv2 license already use proposed above license notices during long time and I have not heard about any issues with this.
-
1) Have you looked at proposed changes? All versions of GPL are available at https://www.gnu.org/licenses/ 2) This is just license notes, but not the license itself. Have you read why they are needed at all? 3) And the final shot: current "postal-address" in your sources is invalid: FSF have moved from "59 Temple Place - Suite 330, Boston, MA 02111-1307, USA." to "51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA." very long time ago...
-
Update license notices
-
Update license notices
1