@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+dr|z3d
+hk
+orignal
+postman
+wodencafe
Arch
DeltaOreo
FreeRider
FreefallHeavens
Irc2PGuest19353
Irc2PGuest46029
Irc2PGuest64530
Irc2PGuest77854
Nausicaa
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
aargh3
acetone_
anon4
b3t4f4c3
bak83_
boonst
cancername
cumlord
dr4wd3_
eyedeekay_bnc
hagen_
khb
mittwerk
not_bob_afk
plap
poriori_
profetikla
rapidash
shiver_
solidx66
u5657_1
uop23ip
w8rabbit
weko_
x74a6
zzz
eyedeekay, I don't know if that's what you wanted, but you just pushed a hundred of your local branches to gitlab/github
eyedeekay
Yup I sure did, no it wasn't what I wanted, meant to send them to my fork, setting up to *carefully* clean them back up
zzz
also, I know I said "in due course", but if you'd like anything significant to be in the next release, you need to step up your MR review game
eyedeekay
Ack, I'll get a couple of them today
zzz
I'm not sure any branches other than master should be on github (or gitlab?). A few have been up there quite a while but this is a lot
eyedeekay
Yeah it was very much an accident, I treat my fork as a backup for my local branches but they weren't meant for i2p/i2p.i2p or i2p-hackers/i2p.i2p
zzz
traditionally, other branches in an official repo would be for currently or previously supported versions, not for experiments...
zzz
I don't know if you want to go thru and delete some of them, or if that's even possible
eyedeekay
Already on it, the official repos will be back to just having the master and the tags in a few minutes, and my branches will be back on my fork where they belong
zzz
super
dr|z3d
for reference, to delete a remote git branch: git push origin --delete <branch_name>
dr|z3d
that command also supports multiple branch delete with: git push origin --delete <branch_name1> <branch_name2> ...