@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+cumlord
+dr|z3d
+eche|off
+hagen
+not_bob_afk
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
Birdy
BubbRubb
Chrono
Daddy
Danny
DeltaOreo
Irc2PGuest19206
Irc2PGuest2981
Irc2PGuest60887
Irc2PGuest88641
Irc2PGuest90985
Irc2PGuest92550
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over
RG
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
Teeed
aargh2
ac9f
acetone_
anontor
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gellegery
makoto
matean
nilbog
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
vivid_reader56
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.