@monsieuricon nice, thank you for sharing this!
I managed to use "git bug bridge {new,pull}", but "git bug push" to g.k.org doesn't seem to do anything. I will need to investigate.
When you have the opportunity, do you mind updating the requirements*.txt files, please? I did the modifications on my side to use pip install in a venv, but I guess you will prefer regenerating these files containing a lot of new hashes than taking my patch :)
@monsieuricon thank you!
I let "git bug push" run in the background, and it only took 57 minutes to finish! In silence...
I now need to figure out what to do to have cgit showing these bugs on g.k.org in the mptcp/linux.git repo :)
@monsieuricon Nooooo 😇 Only 610: https://git.kernel.org/pub/scm/linux/kernel/git/mptcp/linux.git/bugs/
It is currently mirroring https://github.com/multipath-tcp/mptcp_net-next/issues/ , just to see how it looks like (and as a backup, just in case?). I guess it might be hard to move away from the bug system that is in place for a few years. But good to know there are alternatives and it is possible to sync them.
@monsieuricon thank you! Nice work! Funny that the web interface sorts them by creation date, and the TUI by last changed. It might be good to change how they are sorted :)
(same on the "review tui" side in fact, + a way to see all patchwork status :) )
@monsieuricon one thing at a time, thank you for the update!