K. Ryabitsev-Prime 🍁5d ago
"b4 bugs tui" landed in master, but I'm out of time today to write an announcement. Just some very basic scant details here: https://b4.docs.kernel.org/en/latest/maintainer/bugs.html

More tomorrow, along with a proposal how I hope this will help replace bugzilla and augment "just send an email".
bugs: bug tracking with git-bug (alpha) — B4 end-user docs documentation

Show threadMatthieu Baerts4d ago

@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 :)

Show threadK. Ryabitsev-Prime 🍁4d ago
@matttbe Regenerated! Thanks for living on the edge. :) "git bug push" can *definitely* be more verbose about what it's doing.
Show threadMatthieu Baerts4d ago
@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 :)
Show threadK. Ryabitsev-Prime 🍁4d ago
@matttbe 57 minutes seems wrong, though -- you didn't push *that* many bugs.
Show threadMatthieu Baerts

@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.

kernel/git/mptcp/linux.git - Find us on https://github.com/multipath-tcp/mptcp_net-next

Apr 2 at 5:21pmWeb