@eyedeekay
&eche|on
&zzz
+Irc2PGuest3601
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+eche|off
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+snex
Arch2
Birdy
BubbRubb
Chrono
Daddy
Dann
DeltaOreo
Irc2PGuest20149
Irc2PGuest61394
Irc2PGuest65801
Irc2PGuest74254
Irc2PGuest90985
Irc2PGuest95319
Irc2PGuest95708
Irc2PGuest98006
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycl1
T3s|4__
Teeed
aargh2
ac9f_
acetone_
anontor
b3t4f4c3__
cumlord
dr4wd3
duanin2
duck
eyedeekay_bnc
gelleger1
leopold
makoto
matean
mielofon
n1
nilbog
null911
poriori
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
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.