That's a nice, in-depth article. Incidentally, Pijul itself is a pretty interesting project. It's a replacement for git where patches are the primary means of storage. (In git, versions are...
That's a nice, in-depth article.
Incidentally, Pijul itself is a pretty interesting project. It's a replacement for git where patches are the primary means of storage. (In git, versions are primary and diffs are calculated.) This is supposed to be an advantage for repeated merges and cherry-picking. (Darcs is a predecessor that was also based on patches, but it had performance issues.)
It's technically interesting to read about, but they have a long way to go, particularly since git seems good enough in most scenarios.
Thanks for explaining it, I was wondering what the point was instead of just using git. It still seems like really not a big enough problem to put the effort in to make a new tool, but hey,...
Thanks for explaining it, I was wondering what the point was instead of just using git. It still seems like really not a big enough problem to put the effort in to make a new tool, but hey, version control systems need to reproduce somehow... :)
That's a nice, in-depth article.
Incidentally, Pijul itself is a pretty interesting project. It's a replacement for git where patches are the primary means of storage. (In git, versions are primary and diffs are calculated.) This is supposed to be an advantage for repeated merges and cherry-picking. (Darcs is a predecessor that was also based on patches, but it had performance issues.)
It's technically interesting to read about, but they have a long way to go, particularly since git seems good enough in most scenarios.
Thanks for explaining it, I was wondering what the point was instead of just using git. It still seems like really not a big enough problem to put the effort in to make a new tool, but hey, version control systems need to reproduce somehow... :)