Programming

22756 readers

16 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Pijul - DVCS, based on the theory of patches, inspired by darcs (pijul.org)

submitted 2 days ago by Kissaki@programming.dev to c/programming@programming.dev

4 comments fedilink hide all child comments

Pijul is a free and open source (GPL2) distributed version control system. Its distinctive feature is to be based on a theory of patches, while still being fast and scalable. This makes it easy to learn and use, without any compromise on power or features.

Why Pijul

Pijul is the first distributed version control system to be based on a sound mathematical theory of changes. It is inspired by Darcs, but aims at solving the soundness and perfor>mance issues of Darcs.

Pijul has a number of features that allow it to scale to very large repositories and fast-paced workflows. In particular, change commutation means that changes written independently can be applied in any order, without changing the result. This property simplifies workflows, allowing Pijul to:

clone sub-parts of repositories

solve conflicts reliably

easily combine different versions.

The main difference between Pijul and Git (and related systems) is that Pijul stores changes (or patches), whereas Git deals only with snapshots (or versions).

you are viewing a single comment's thread
view the rest of the comments

[–] cyclohexane@lemmy.ml 4 points 2 days ago (1 children)

It's hard to understand what exactly will change for me if I used pijul vs git. What will be noticeably different?

[–] Oinks@lemmy.blahaj.zone 7 points 1 day ago (1 children)

I can't speak for everyday workflow (having discovered this project less than a week ago), but rebase being unnecessary and cherry-pick not creating duplicate commits seem like the most notable advantages to me.

[–] cyclohexane@lemmy.ml 1 points 9 hours ago

When working with git, and I have a separate working copy, my options to sync are either rebase or create a merge commit.

It sounds to me like the pijul workflow is almost equivalent to just doing a merge commit instead of rebasing. Am I correct here? What's the difference then?