<thomasbuilds:matrix.org> Was going through monero github repos and noticed kovri is set as public archive yet kovri-docs and kovri-site aren't

<thomasbuilds:matrix.org> kastelo should be archived too?

<ofrnxmr:xmr.mx> @thomasbuilds:matrix.org: Kastelo lol

<ofrnxmr:xmr.mx> id argue that kastelo should be migrated to msvb's personal repo and deleted from monero-project

<thomasbuilds:matrix.org> Yeah wherever it's about deleting or archiving it's not up to me. But yeah I'd delete it.

<thomasbuilds:matrix.org> mrelay.p2pool.observer/m/matrix.org/MmmNQTxPChqvIMbkNumnURRi.png (Screenshot from 2026-07-22 09-25-30.png)

<thomasbuilds:matrix.org> should also pin gitan sigs repo

.merges

10747 10823 10863 10876 10894 10921

.merge+ 9828

Added

Msg

.merge+ 10896

Added

.merge+ 10358

Added

.merges

10747 10863 10876 10894 10921

.merges

10747 10876 10894

.merge+ 10694

Added

is it preferred to re-indent 100+ lines, or is it okay to add 3 lines without correct indentation for a patch?

<ofrnxmr:xmr.mx> The 100 lines are incorrect and the 3 lines match it?

found a different solution anyway

no my question was something else, current code is correct but my patch would add new { } which would change indentation

but i found a solution now without adding { }

Is that code for... goto ? :D

I'm pretty sure I already made at least one patch doing just that (adding extra test and {} but leaving existing code as is without reindent). I typically add extra newlines at the { and } places to make things clear. 100+ lines reindent is way too large and will cause pain and conflicts. I sometimes do the reindent in TF but only because I'm the only one working on it. It's inconsiderate

otherwise. Though I'm sure some will say it's inconsiderate to go the other way.

<jeffro256> It's a trade-off for pain now and pain later. No re-indent makes the code much harder to read and maintain. Re-indenting now means the git blame is messed up, and requires a reviewer to make sure that the lines are copy and pasted correctly.

<jeffro256> As someone who is updating a decent amount of code, and keeps stumbling upon indentation inconsistencies, I'm really starting to prefer just doing the indentation correct now

no goto, it just has a bit longer lifetime now but should not matter

<jeffro256> BTW I'd like to review beg for #9827, a pre-req for carrot_core

I agree with jeffro, also git blame -w exists

<jeffro256> And git diff -b