3 ms·
This just needs to ditch all of the command line stuff and explain the patch concept up-front. This was the most useful line: > if we unrecord a patch with dep
by IshKebab 8y ago
This just needs to ditch all of the command line stuff and explain the patch concept up-front. This was the most useful line:
> if we unrecord a patch with dependencies all its dependencies are unrecorded as well.
Up until that point I had been thinking "but what happens with patches that depend on each other", and I don't think they really explain that ever on the Pijul website.
But it doesn't go far enough - how is the dependency automatically tracked for example?
- WorldMaker 8y agoAutomatic dependency tracking is deceptively simple: If you think of a patch as something as simple as "Modify line 10 of file A from `dog\n` to `cat\n`", the dependency is obvious: whichever previous patch left `dog\n` in line 10 of file A. In most cases that's good enough to get stuff done. Of course, it's not automatic semantic dependency tracking. It can't always entirely tell that Patch B depends on a "feature"/"flag"/"magic bean" in Patch A or it won't CI build, without additional information (such as a CI build process in a bisect, or a manual dependency flag from the author of Patch B or a downstream consumer).