@kensanata I have three questions on your migration to #cgit from #github. What made you pick it over the other options, including #fossil (which I know is different)?
Are you going to put in an easy place where people can access the repos to clone publicly? I found your method of patching pretty easily (email you diffs) but noted the public access was in a comment (somewhere).
Are you using #debian? I notices cgit didn't have a package for it upstream.
@PresGas I am using Debian and there was a cgit package. A https link is provided by cgit for every repo. I didn’t use fossil because I want to keep using git because of side effects: we use git at work and so this is “practice”.
@kensanata Yeah, I have seriously thought about this practice too. It is nice to see it is small and c as well. For some reason, that was a big nice thing for #fossil was its c roots.
@PresGas having written something in C last year I can no longer understand why people like programs written in C. These programs are terrible! The only thing that makes sense is if people like to use very old programs written in C that passed the test of time, I guess?
Spontaneous poetry time!
«Free and malloc crash
Did I do something rash?
Hm. C what I did there?»
@kensanata *SNORT!* That was funny! I guess it was attractive to me that #fossil was one binary app with no deps...
Note also that I cannot program my way out of a wet paper bag, so take what I say with caution.
