Live data from Hacker News

Pijul a FOSS distributed version control system

pijul.org

31–32 of 32 posts

Re: Pijul a FOSS distributed version control system

#31

Earlier quoted context omitted.

Git's patching functionality is pretty awful in actual practice. For example, try building a git patch that applies a standard set of patches between two divergent (vendored) kernel trees. It's usually a mess. It's also pretty easy to find a set of patches that have to be applied in order. Then someone copies those patches onto another divergent tree, which has it's own set of custom patches without renaming. This is…

I think patching/cherry-picking is just inherently complicated and needs intelligence applied. I don't think Pijul is going to be any better here.

That is kind of the point of Pijul, first class support for "how do I combine these" which git mostly discards as unimportant.

But for a lot of work at scale (or people) mixing bits is important.

Re: Pijul a FOSS distributed version control system

#32
post #20

Earlier quoted context omitted.

Speaking as a former Darcs user (Darcs is another patch-based VCS that Pijul draws inspiration from): "This is a useless property because the graph is only encoded at the patch layer. In the real world you have far more semantic dependencies than patch dependencies. ie, I have a patch that adds a function that calls a function added in another patch. Pijul doesn't know about that." Darcs solved this in two different…

What I want is a system that records how conflicts are resolved and tries to apply that resolve. Lets say I have apply patch A, then patch B, there is a conflict, I resolve it. Then someone else applies patch B and then patch A. The VCS should know that this conflict is already resolve and apply the solution. Likewise when applying first patch C, then A and B, it should let you resolve the conflict from AB to ABC and…

I believe this is what `git rerere` does
Post reply on HN