Just re-upping this offer: because being comfortable with git is a barrier to entry to many FS/OSS projects, and because I care deeply about lowering those barriers, I will tutor anyone who asks for help with git, and/or connect them with any mentor(s) they might prefer.
I'll do this while I put energy and work into making the tool more approachable, and into making better tools and learning paths.
Boosts gratefully appreciated.
So it's 37kg, 2ft wide and I have IDEAS. Not sure if I'm going to carve 6 faces into it or two big faces and fill in the rest with stars, spirals and ornate patterning, but it'll be one of those.
Square and oval eyes, star and square eyes.
Or triangle eyes maybe, not tried that yet. Features should be deeply sculpted, it's solid so plenty to ensure it won't collapse 😊
Risk is ornate patterns like this. Looks great but weakens support, lesser patterns leave a lot to hold it together
#gameoftrees 0.18 is out! Highlights among the changes:
branches can now be merged easily ('got integrate' was added)
3-way merge conflicts now show content from all 3 input files, not just from 2
executable files becoming non-executable and vice-versa is properly handled
tog searches through commits a lot faster
your log messages are no longer deleted when an error occurs
I am also considering pgBackRest for PostgreSQL backups
anyone here use it?
If your makefile is just a fancy shell script that runs some commands sequentially without using make's dependency resolution, just write a shell script.
If you want to rebuild everything from scratch every time, just make your build script a shell script.
The whole point of writing a makefile is to tell make which files depend on what other files, and have it only rebuild things when necessary. Ideally, you should have one command per rule, and let make take care of your control flow.
If you want to roll your own control flow, just write a shell script.
Devices that have any sort of data collection or other “phone home” functionality should come with an easy to understand written-on-paper standardized disclaimer, just like washing machines come with energy use into or cars have gas consumption info in the window when you. It them.
When there’s any change (e.g. due to software updates), costumers should@get mandatory updates in the form of a written paper letter and email.
As always, buying books at park gift shops and keeping up on regional cryptid stories. This critter on the cover is Shuswaggi, the Shuswap Lake monster. https://www.columbiavalleypioneer.com/trending-now/have-you-heard-the-legend-of-shuswaggi-the-shuswap-lake-monster/
I went to see War, an Indian action film. So good. Just the kind of mindless entertainment I was after. A cross of Bourne and Mission Impossible. Beautifully choreographed action scenes.
But it's an Indian movie, so of course Jason Bourne and Ethan Hunt take a break from the action to perform a dazzling dance number in full colour:
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!