06:58:17 <br-m> <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
07:01:45 <br-m> <thomasbuilds:matrix.org> kastelo should be archived too?
07:02:30 <br-m> <ofrnxmr:xmr.mx> @thomasbuilds:matrix.org: Kastelo lol
07:04:34 <br-m> <ofrnxmr:xmr.mx> id argue that kastelo should be migrated to msvb's personal repo and deleted from monero-project
07:24:04 <br-m> <thomasbuilds:matrix.org> Yeah wherever it's about deleting or archiving it's not up to me. But yeah I'd delete it.
07:25:57 <br-m> <thomasbuilds:matrix.org> https://mrelay.p2pool.observer/m/matrix.org/MmmNQTxPChqvIMbkNumnURRi.png (Screenshot from 2026-07-22 09-25-30.png)
07:25:58 <br-m> <thomasbuilds:matrix.org> should also pin gitan sigs repo
07:36:34 <tobtoht> .merges
07:36:34 <xmr-pr> 10747 10823 10863 10876 10894 10921
10:22:48 <selsta> .merge+ 9828
10:22:48 <xmr-pr> Added
12:04:30 <daster> Msg
14:29:33 <selsta> .merge+ 10896
14:29:33 <xmr-pr> Added
16:08:07 <selsta> .merge+ 10358
16:08:07 <xmr-pr> Added
16:17:00 <tobtoht> .merges
16:17:00 <xmr-pr> 10747 10863 10876 10894 10921
19:05:28 <tobtoht> .merges
19:05:28 <xmr-pr> 10747 10876 10894
19:13:54 <selsta> .merge+ 10694
19:13:54 <xmr-pr> Added
19:47:19 <selsta> is it preferred to re-indent 100+ lines, or is it okay to add 3 lines without correct indentation for a patch?
19:52:23 <br-m> <ofrnxmr:xmr.mx> The 100 lines are incorrect and the 3 lines match it?
19:52:51 <selsta> found a different solution anyway
19:54:25 <selsta> no my question was something else, current code is correct but my patch would add new { } which would change indentation
19:54:37 <selsta> but i found a solution now without adding { }
19:58:07 <moneromooo> Is that code for... goto ? :D
19:59:00 <moneromooo> 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 
19:59:06 <moneromooo> otherwise. Though I'm sure some will say it's inconsiderate to go the other way.
20:06:59 <br-m> <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. 
20:08:19 <br-m> <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 
20:08:59 <selsta> no goto, it just has a bit longer lifetime now but should not matter
20:10:20 <br-m> <jeffro256> BTW I'd like to review beg for #9827, a pre-req for carrot_core 
20:10:41 <tobtoht> I agree with jeffro, also git blame -w exists
20:13:05 <br-m> <jeffro256> And git diff -b