@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+dr|z3d
+eche|off
+hagen
+orignal
+postman
+snex
+wodencafe
Arch2
Danny
DeltaOreo
FreeB
Irc2PGuest59134
Irc2PGuest59581
Irc2PGuest70083
Irc2PGuest96449
Irc2PGuest97049
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4
acetone_
aeiou
ardu
b3t4f4c3___
bak83_
boonst
carried6590
cumlord
death
dr4wd3
duck
eyedeekay_bnc
mareki2p
not_bob_afk
onon_
phobos
pisslord
poriori_
profetikla
qend-irc2p
radakayot_
rapidash
shiver_1
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
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.