@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN_
+acetone
+dr|z3d
+hk
+lbt
+orignal
+postman
+weko
+wodencafe
An0nm0n
Arch
Dann
DeltaOreo
FreefallHeavens
GucciferZ_
Irc2PGuest35128
Irc2PGuest43186
Irc2PGuest56267
Irc2PGuest59134
Irc2PGuest61987
Irc2PGuest99418
Leopold
Nausicaa
Onn4l7h
Onn4|7h
Over1
RN
Sisyphus
Sleepy
SoniEx2
T3s|4
T3s|4_
anon
b3t4f4c3__
bak83
boonst
carried6590
cumlord
dr4wd3
eyedeekay_bnc
l337s
not_bob_afk
poriori_
profetikla
qend-irc2p_
r3med1tz-
radakayot_
rapidash
scottpedia
shiver_
solidx66_
syncthing2
trust
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.