Fossil https://fossil-scm.org is forum, chat, bug tracker, wiki. And a distributed version control.
Fossil https://fossil-scm.org is forum, chat, bug tracker, wiki. And a distributed version control.
Oh man how cool Fossil is! I updated the Goophy devlog entry on my gopher hole and with just one command: ' fossil commit -m "Update Goophy Devlog" ', it commited the changes and synced them with my remote fossil server.
@krisajenkins regarding the "Solving Git's Pain Points with Jujutsu" episode, for a little bit of a counter example about a "universal" technology I have been able to develop software mostly ignorant of #Git and use #FossilSCM instead. I'm an odd case, but a good example of how other tech stacks can reach non developers and being more aproachable by a general public.
Maybe you could consider Richard Hipp from #sqlite / #fossil fame?
As usual, excellent epidode:
Git might be the most ubiquitous tool in software development, but that doesn't mean it's perfect. What if we could keep Git compatibility while fixing its most frustrating aspects—painful merges, scary rebases, being stuck in conflict states, and the confusing staging area? This week we're joined by Martin von Zweigbergk, creator of Jujutsu (JJ), a Git-compatible version control system that takes a fundamentally different approach. Starting from a simple idea—automatically snapshotting your working copy—Martin has built a tool that reimagines how we interact with version control. We explore the clever algebra behind Jujutsu's conflict handling that lets you store conflicts as commits and move freely through your repository even when things are broken. We discuss why there's no staging area, how the operation log gives you powerful undo/redo capabilities, and why rebasing becomes trivially easy when you can edit any commit in your history and have changes automatically propagate forward. Whether you're a Git power user frustrated by interactive rebases, someone who's lost work to a botched merge, or just curious about how version control could work differently, this conversation offers fresh perspectives on a tool we all take for granted. And if you're working with large monorepos or game development assets, Martin's vision for the future of Jujutsu might be exactly what you've been waiting for. --- Support Developer Voices on Patreon: https://patreon.com/DeveloperVoices Support Developer Voices on YouTube: https://www.youtube.com/@DeveloperVoices/join Jujutsu (JJ): https://github.com/martinvonz/jj Jujutsu Documentation: https://martinvonz.github.io/jj/ Git: https://git-scm.com/ Mercurial: https://www.mercurial-scm.org/ Rust: https://www.rust-lang.org/ Watchman: https://facebook.github.io/watchman/ Google Piper: https://research.google/pubs/why-google-stores-billions-of-lines-of-code-in-a-single-repository/ Kris on Bluesky: https://bsky.app/profile/krisajenkins.bsky.social Kris on Mastodon: http://mastodon.social/@krisajenkins Kris on LinkedIn: https://www.linkedin.com/in/krisjenkins/
Hi guys, I know this risk to become the dumbest question ever made on the #fediverse but I must ask it not matter what…
For all the experts and non-experts… Is it possible, or would it possible, to have a plain text image format?
Something that can be diffable and you can track changes as for instance the #SVG format. It looks like all these control versions, like #git, aren't very suitable to handle format like #png, #jpg ,etc… They can only handle them as a binary blob and track if it has changed and re-upload or re-download fully.
Long-story short: handle the creation of catalog with #Fossil-scm hasn't been very good regarding managing the huge amount of pictures…
Fossil-scm help
#fossilscm expert I need your help...
The repo on the server has an error on a hash:
size mismatch on artifact 1271: wanted 261534 but got 0
wrong hash on artifact 1271
954 non-phantom blobs (out of 1297 total) checked: 2 errors
low-level database integrity-check: okHow can I fix it?
From the local machine I can't do anything:
fossil update
SQLITE_NOTICE(539): recovered 9 pages from /home/me/sp/projects/ctlg0.fossil-journal
Pull from ssh://me/sp/ctlg0.fossil
bind [127.0.0.1]:12000: Address already in use
Round-trips: 1 Artifacts sent: 0 received: 0
wrong hash on received artifact: 3661aa5b091f6eb3937419b05697b7ddc0e645cab2a5cf0e6a95fcc20203fe5f
Round-trips: 1 Artifacts sent: 0 received: 12
hash of rid 889 does not match its uuid (
fish: Job 1, 'fossil update' terminated by signal SIGABRT (Abort)Is there any magic command to auto repair or discard that hash?
Thanks in advance!