i’m running a code sharing service for humans here, not a piece of computing infrastructure; if you want reliable computing infrastructure i encourage you to manage your own repo on your own platform
why? because i’m not interested in hosting broken code, and because you should be using hashes not tags for anything you need an immutable identifier for
“but using a hash doesn’t help if that hash ceases to be available” i’m not interested in hosting broken code
my git policy by the way is that versions before the latest are immutable; anything goes after that point
i can and do retag latest versions and do fixups on them
there are lots of new features i want to add, some of which are really useful!! but i’m refusing to do so until i have a proper release of what i have
i basically had this feature-complete shortly after i published 0.9.3
don’t let versions 0.9.4 thru 0.9.6 fool you, they are bugfixes rebased backwards in time
and then look at how many commits since 0.9.6
i mean not the part where they travel to the heavens and leave behind a triforce but the other part
is there anything i care about in this? probably not, they wouldn’t tell me if there was, and nobody is going to actually implement it anyway
Posix 2024 was published?? https://pubs.opengroup.org/onlinepubs/9799919799/
Administrator / Public Relations for GlitchCat. Not actually glitchy, nor a cat. I wrote the rules for this instance.
“Constitutionally incapable of not going hard” — @aescling
“Fedi Cassandra” – @Satsuma
I HAVE EXPERIENCE IN THINGS. YOU CAN JUST @ ME.
I work for a library but I post about Zelda fanfiction.