@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+RN_
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+robin
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
HowardPlayzOfAdmin
Irc2PGuest14159
Irc2PGuest28800
Irc2PGuest93285
Onn4l7h
Over
Sisyphus
Sleepy
SlippyJoe_
Stormycloud_
T3s|4
T3s|4_
Teeed
ac9f
acetone__
ardu
b3t4f4c3__
bak83_
coolbuddy799
dr4wd3_
duanin2
duck
eyedeekay_bnc
kaffi
leopold_
makoto
marek22k
nilbog
not_bob_afk
poriori
pory
profetikla
r00tobo_BNC
rapidash
shiver_
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr_
obscuratus
I'll have to step back and scratch my head a little on how to subit my Merge Requests. They touch just enough stuff across several branches to make it confusing.
obscuratus
eyedeekay: I put together a Merge Request for my banlist refactoring, but I had to make it against i2p.i2p.2.4.0-test1 since it affects both i2p.i2p.2.2.1-nested-netd and some stuff already merged from 2.3.0-lookup-tweaks.
obscuratus
I couldn't figure out another way to do it, but it probabaly will make things difficult in the i2p.i2p.2.2.1-nested-netd branch as long as that branch doesn't know about the 2.3.0-lookup-tweaks and the banlist refactoring.
obscuratus
So let me know if there's another way you'd like me to try to go about this MR.