On Thu, 2021-04-15 at 15:55 +0200, Henrik Sandklef wrote: > First of all, thanks for looking in to this.
Oh, I didn't expect you to be subscribed, thanks for that. > My name is Henrik Sandklef and I (poorly) maintain GNU Xnee. Thanks for that too. > Not enough to make a new release I am afraid. > So, those plans are moved to /dev/null. No problem. > https://github.com/hesa/gnu-xnee > https://github.com/hesa/gnu-xnee/commit/233d0a3e45b2ad86319d3372916ddd61b26cb5f6 > https://cvs.savannah.gnu.org/viewvc/xnee/xnee/NEWS?r1=1.110&r2=1.111 If you have time, I would suggest a few potential actions: Try to re-do the conversion from CVS to git using reposurgeon, since it produces a better conversion. I wrote the attached draft cvs2git script that uses reposurgeon and then does some cleanup on the repository with git and git-filter-repo. It is fairly complete. In particular it drops bogus log messages, adds git style authors and converts CVS tags and branches to git tags and branches. Please review the script and the resulting git repository before using it though. http://www.catb.org/esr/reposurgeon/ https://github.com/newren/git-filter-repo Delete and recreate the GitHub repository. Push the new git conversion to GitHub. Enable git in the Savannah project and push to the repository. Remove the CVS repository for the code from the Savannah project. Decide on whether you want GitHub or Savannah or both for hosting. > Re-added "/xnee" to sandklef.com. Thanks. > [1] cert only valid for sandklef.com (not www.sandklef.com). If > problematic, can we change the homepage to "sandklef.com/xnee" If you control the server, it should be fairly easy to add both domains to the Lets Encrypt certificate config. Of course changing the Homepage to the working domain or to xnee.wordpress.com is fine too. PS: I note the GNU link on https://sandklef.com/ is broken too. -- bye, pabs https://wiki.debian.org/PaulWise
cvs2git
Description: application/shellscript
signature.asc
Description: This is a digitally signed message part
