Consider merging or overwriting history with unofficial fork
Opened this issue · 3 comments
Hi Tom,
I’m glad that rinetd has some online presence again! I would like to suggest replacing this repository’s history with that of the fork I’ve been maintaining for the last 15 years (currently at samhocevar/rinetd) that has dozens of improvements and bugfixes. I’d be sad to lose that history if your repository becomes the main place for rinetd.
Here is a summary of the major changes:
- UDP support, IPv6 support
- source address binding support
- fixed various memory leaks, uninitialised data access, and buffer overflows
- improved performance
- use a grammar-generated parser to parse the configuration file
- autoconf project for feature detection for Unix systems
- Visual Studio project file for Windows systems
- cross-compile on Linux for Windows
As you say that's an impressive amount of work that's been done. Is this also considered the upstream version by any repos that are distributing rinetd at this point?
What I'm considering here is that I should probably pass the baton to you officially and link to that rather than the repo I've been "maintaining" so lackadaisically.
It's clear from what I'm seeing in your repo and in Debian's maintainer notes that you are for all intents and purposes the official maintainer of rinetd, if you want to be. Shall I just redirect all the things?
I apologize for not doing this sooner.