@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Daddy_
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest5865
Irc2PGuest92548
Leopold
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
Teeed
ardu
b3t4f4c3___
bak83
boonst
cumlord
death
dr4wd3_
eyedeekay_bnc
not_bob_afk
not_human
nuke
onon_
poriori
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
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.