IRC channel logs

<oriansj>now this is an interesting idea: https://gist.github.com/median-man/3a7c4324005e96f02691f3a20aeac26b default commit templates as part of git repo

<oriansj>anyone know of a really good template?

<oriansj>it literally it just add a .gitmessage file with the desired template and git config commit.template '.gitmessage'

<oriansj>when commiting it shows up but all of the commented lines are dropped when the message is commited.

<oriansj>well I've opted to create a sourcehut account

<oriansj>and as promised, I will be creating a dotfiles repo for sharing and after some work my notes too

<oriansj>which looks like no one but me cares about

<fossy>there are many ways to template git messages

<fossy>its very important in larger git repos

<oriansj>fossy: fair, just seems like a good idea to include the template in the repo which it is to be used in.

<oriansj>and now people can judge my config harshly: https://git.sr.ht/~oriansj/config

<oriansj>I'll probably have some cleanup and missing bits to sort out too

<oriansj>and I'm gonna setup a mirror of the wiki on sourcehut too as part of a project called bootstrappable

<oriansj>well the wiki clone looks ugly: https://man.sr.ht/~oriansj/bootstrappable/

<oriansj>now how to grant write access?

<theruran>is there a DOT diagram of the bootstrap path from hex0 to GCC?

<oriansj>theruran: yeah: https://github.com/oriansj/talk-notes/blob/master/live-bootstrap.dot (it is a little old but it is largely correct)

<oriansj>I probably should start unifying the bootstrap notes I have with the wiki

<oriansj>which reminds me ekaitz I don't think ever got a pull for your fosdem 2022 talk slides to add to the bootstrapping talk list

<theruran>oriansj: christ. yep, this is what I was looking for. Thanks!

<ekaitz>oriansj: oh i didn't think about adding that there

<ekaitz>oriansj: feel free to add it! https://fosdem.org/2022/schedule/event/riscvadventures/

<ekaitz>or should I do it myself?

<oriansj>I can do it in a couple hours but if you do it before then, I'll be certain to merge your improvements ^_^

<ekaitz>oriansj: I'm trying to stay out of the screen now, so feel free to do it :)

<oriansj>ekaitz: ok

<aggi>gladly, it is still possible to use perl-5.8.6, only two minor patches to pass with autoconf-2.7 and some latest automake version

<aggi>meaning, perl-5.8.6 can both be bootstrapped with tcc-toolchain. and it still works with gentoo and the package set chosen

<aggi>at least the the entire package set of ~600 builds passed compilation with this, and wherever autoreconf is called, which it is very often

<aggi>GNU gettext too was a trouble source with tcc-toolchain, it's completely removed now, only a dozen minor hacks, not require compile-time nor run-time anymore

<aggi>almost done with the gcc47-toolchain freeze and archival, and the entire distro for this

<aggi>i'll re-try tcc-toolchain with arm-tcc this night, to emit a mes-libc/toybox userspace compiled/linked/assembled without any GNU gcc/binutils

<oriansj>now the real question is should I publish my whole Dr Stone-like notes collection or just those I think people will probably find interesting

<vagrantc>/30/30

<oriansj>vagrantc: ???

<vagrantc>oriansj: channel-switching typo, sorry :)

<oriansj>lol

<unmatched-paren>oriansj: You should probably convert those == ... == headers to ## ...

<unmatched-paren>or # ... for top-level headers i guess

<unmatched-paren>Also, iirc sourcehut supports autogenerating TOCs

<unmatched-paren> https://man.sr.ht/man.sr.ht/ <- very meta :)

<unmatched-paren> https://man.sr.ht/meta.sr.ht/ <- even more meta... :P

<unmatched-paren>Hmm, looks like the TOC is enabled by default

<unmatched-paren>it should look something like https://paste.sr.ht/~unmatched-paren/17658713bc069a6c40525724df55b558da03bae5

<unmatched-paren>sorry, https://paste.sr.ht/blob/a5bdd258fc9a916fd4e72c62ff00dc8cb1cf7260