@eyedeekay
&zzz
+Irc2PGuest59076
+RN_
+Stormycloud
+T3s|4
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest13210
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest32330
Irc2PGuest5631
Irc2PGuest74254
Irc2PGuest78101
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
SlippyJoe
T3s|4__
Teeed
aargh2
ac9f_
acetone_
anontor2
b3t4f4c3__
dr4wd3
duanin2
erniee
eyedeekay_bnc
gellegery
leopold
makoto
marek
n1_
nilbog
noidea_
onon_1
poriori_
profetikla
r00tobo
rapidash
shiver_
thetia
tr
u5657
uop23ip
vivid_reader56
w8rabbit
wodencafe2
x74a6
zelgomer
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.