@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+hk
+postman
+qend-irc2p
+snex
AHOH
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreeB
FreefallHeavens_
Irc2PGuest21522
Irc2PGuest31517
Irc2PGuest51104
Leopold_xmpp_
Onn4l7h
Over1
Sisyphus
Sleepy
StormyCloud
T3s|4_
Teeed
aargh
acetone
ardu
b3t4f4c3___
bak83_
cumlord
death
dr4wd3_
dr|z3d
duanin2_
duck
eyedeekay_bnc
hagen_
makoto
mareki2p_
nilbog-
not_bob_afk
ohThuku1
orignal
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
wodencafe2
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.