Every now and then I get questions on how to work with git in a smooth way when developing, bug-fixing or extending curl – or how I do it. After all, I work on open source full time which means I have very frequent interactions with git (and GitHub). Simply put, I work with git all day long. Ordinary days, I issue git commands several hundred times. I have a very simple approach and way of working with git in curl. This is how it works.
Git is hard: messing up is easy, and figuring out how to fix your mistakes is impossible. Git documentation has this chicken and egg problem where you can't search for how to get yourself out of a mess, unless you already know the name of the thing you need to know about in order to fix your problem.
When the Linux 5.8 Release Candidate opened for testing recently, the big news wasn’t so much what was in it, but its size. As Linus Torvalds himself noted, “despite not really having any single thing that stands out … 5.8 looks to be one of our biggest releases of all time.” True enough, RC 5.8 …
GOMP is a Git-based tool for comparing branches, designed to work with a rebase-oriented Git workflow. Markforged uses GOMP as both a daily tool for handling commits and merges and as a powerful way to visualize complex histories while preparing releases.
Gitception is the idea of putting your Git repository in a Git repository to see what Git does when Git is used. It is a different approach to learn Git. Git is not a tool that just works. Most users memorized a list of commands to sync up but don’t know what happens. It may throw errors at some point or you might get lost with branches. Therefore it certainly helps to understand how it works and that, for example branches are no magic, delete a branch is not dangerous and why creating branches is so fast. To see the internals of Git helps you learn the concepts behind and can create aha-moments because if you are in a situation that doesn’t follow the happy path you would have expected, you will be able to understand what is happening and why.
repoSpanner is a distributed repository storage server, based around Git.
It is designed so that all nodes are equal -- any client can push/pull to/from any node and should see no difference at all. Each node makes sure that all pushed objects are synced to at least a majority of the nodes before acknowledging the push.
The system should be resilient against any nodes failing, as long as a majority of nodes remains available; with the worst case being a single push failing due to an attempt to push to the failed node.
FoldFold allExpandExpand allAre you sure you want to delete this link?Are you sure you want to delete this tag?
The personal, minimalist, super-fast, database free, bookmarking service by the Shaarli community