I think this sounds nice but it feels difficult to me. The easiest plugins to write would be s-expressions and JSON, and I could definitely see myself choosing Pijul for such repos in the future. ), but they'd (a) be more complicated and (b) more subject to churn. Pijul 0.3, our first bootstrapped release! Any diff you see is just for display purposes or for input to the three-way merge algorithm. hide. I came up with that name, but to be honest, I was more interested in getting stuff to work (which was challenging enough) than in thinking about names at that time. Please correct me if I have! Thanks. Also, merging (especially automatically) is limited by the quality of the data. EDIT : Oh crap : * The index of packages on crates.io is stored in a git repository, * Cargo knows how to clone that down without you having git installed. > someone submitting stolen work to a fellow he stole the work from. For a time, I was tracking some of them to figure out which ones support which particular protocol extension; the result is https://ssh-comparison.quendi.de and the list there is really incomplete (and sadly also outdated -- PRs welcome ;-)), I think I could easily double the number of entries there if I resumed work on it. But I don't think that's how licenses like the GPL work? I agree with the above poster that if graphical user interfaces prioritized it better, if the CLI had a bit fewer warts (I still often confuse when to use `git add --patch` and when to use `git add --interactive` though it isn't an awful confusion because you can get to one from the other when you remember how to use it), and if tutorials tried better to train people on the tools that already exist, a lot more people would presumably use them (daily in some cases). It takes multiple seconds for that page to open, and then it shows me "Not found". 2. the whole merge/rebase dichotomy. Coming from a darcs background where that was a natural and very easy part of the UX, I had reason to learn how to do it in git (because I was used to doing it quite often in darcs). One of Pijul's main selling points is the ease of cherry-picking. [1] https://github.com/WorldMaker/tokdiff, (ETA: Suppose the first step is that it is time to get the band back together and update the prototype to Python 3.). When people watch me do it, they can't believe that magic exists in git. It seems that this results in review tools bending backwards to add that on top and it makes backports and other cherry-picks harder to follow. One advantage to using a syntax highlighting tokenizer/lexer is that they are designed to be fast (many of them need to be real time in text editors after all), and handle "degenerate cases" very well (text editors spend a lot of time on work in progress code that doesn't fully describe a complete compilable unit; version control systems just as well need to be good at storing work in progress states). Future possibilities: This would make it possible for the user to create a shortcut status command equivalent to that command of darcs ( darcs status ). That's actually the case, because you can totally simulate Git using Pijul if you want, except for the weird merges where Git shuffles up lines randomly. I guess it doesn't matter as long as it works /shrug. … And need to have a custom server and protocol. And distribute that by default as well, otherwise everyone defines their own mutually incompatible aliases. We strive for transparency and don't collect excess data. Let's say I have a patch A that adds a line: At the end of the article it says that the rename (to Anu) has been reverted. I really have invested time into this to try to get a proper understanding. Ssh deals with keys and accounts and all that which SSL/TLS don't do. Disclosure: as someone who was trained as a mathematician, I’m offended by attempts at restricting the free exchange of knowledge. This is a very elegant solution and arguably a more natural way to create such a … Has some issues like: move not showing from where it is being moved; ineficient implementation ; A [file] might be an untracked or tracked file. This means that this feature is mostly useful for end projects and private libraries, not public dependencies. for the command-line. You would need cargo to compile it from source anyway. braces), e.g. With you every step of your journey. - The project got renamed to Anu. Anu was at least pronounceable without doing a few double takes. This thread is archived. https://www.youtube.com/watch?v=OSWszdSHkyE. Would I want to put myself at legal risk, just because I want to try an experimental VCS? If the patch-based approach is truly as nice as it appears, that might push me to use it more generally. I'm the author, I understand how that comment of mine could be misinterpreted, which is why I removed it. That's some A level chicanery. The notation [0, n[ is standard in Germany. But that was rather the point: "I'm an egotistical bastard, and I name all my projects after myself. I also came here to comment on this. FWIW, I liked the name "Anu" better. I've also seen partial reimplementations of Pijul, from the source code, with a different license, which is absolutely clear. First reason: writing servers that are easy to secure and maintain. I've been keeping an eye on Pijul for a while, but assumed that (when it eventually stabilised) it personally wouldn't be worth the effort to switch from git. Darcs is the "smart" to git's "dumb" and Pijul is exploring if you can have "smart" without sacrificing "fast". It's a lot of characters to type all on the right hand (in QWERTY). In other words, Pijul works in polynomial time for all patches that systems other than darcs know of. - Pijul patches were storing raw lines of text, - Word-based diffing was suggested as an option, - This option wasn't implemented due to complexity, and having to decide at repo creation time whether to store lines or words, - Unrelated improvements to Pijul's performance resulted in patches storing offsets into a byte array, rather than raw text, - Since offsets can point anywhere, patches are no longer limited to being line-based. Wait few years until we finish new shiny graphical UI first! The Haskell DVC system that pijul "sort of" evolved from (theory of patches-wise mostly, just being careful given the stringent IP/credit language afoot), darcs, had this sort of semantic concept. Yes, it does, even if the interface might be somewhat lacking, and the documentation work in progress. I haven't looked at darcs in many years, but it would be unsurprising if it had evolved to similar generality like … https://en.wikipedia.org/wiki/Islamic_Jihad_Movement_in_Pale... Well, at least it didn't change the name to another (than 'Anu') ancient god : Isis ! Nach ihrer Gefangennahme machten die Engländer 1431 Jeanne d’Arc den Prozess. Thanks! As I … Do you know, that calling someone a git is an insult? The gpl doesnt protect ideas, it only protects code. ATM don't have time to read in depth but can someone explain if Pijul allows a user to checkout a subset of changes (say I only checkout one folder or a file)? I haven't looked at darcs in many years, but it would be unsurprising if it had evolved to similar generality like pluggable byte ranges. - Although most patches are inversible in Pijul, patches resolving conflicts are not. I guess that the author might be an astronomy aficionado ? Right, there have been really strong reactions against that move. There seems to be no way to simply rollback a change if some newer change depends on it (so we can’t use unrecord). Still a tiny fraction compared to available tokenizers in Pygments: Encoding a generic, potentially versioned AST in S-expressions seems feasible. save. (It's so very common to work on things side-by-side and then want to split things out into more logical commits to describe things as individual changes.). ), Haskell is not my usual habitat. I clicked on the "nest" link (hoping for a download source tarball button), but this link 404s: https://nest.pijul.com/pijul_org/pijul, Possibly this is the right home for pijul: https://nest.pijul.com/pijul/pijul, I cannot find an issue tracker. Of course it does. We’ve not yet thought all the theory of this through, but it might be added in the future. Hi darcs fellows, Florent Becker and myself are proud to announce the second public release of Pijul, a new version control system aiming to be easy to learn and use, distributed, and fast. Next message: [darcs-users] new darcs maintainer: Guillaume Hoffmann Messages sorted by: Dear darcs acolytes, Pierre-Étienne Meunier and myself are honoured to present version 0.1 of Pijul. But then I managed to find another distracting thing, by writing a rant about occurrences of plagiarism that have happened to me, including theft of actual GPL source code, as well as republication of academic papers (in one case, I was fortunate enough to be picked for review). My idea that I’ve bandied about here a few times would be to create some kind of a semantic database (not based on relational algebra). I'm really excited to see what Pijul ends up doing. DEV Community © 2016 - 2021. Once a conflict is solved in Pijul, it's solved by a patch, and solved forever. [1]: https://en.wikipedia.org/wiki/Interval_(mathematics). It is not a drawback at all, there are no downsides to it, and we get the very serious benefit that merges are associative, which is not the case in Git. button. > That's actually the case, because you can totally simulate Git using Pijul if you want, except for the weird merges where Git shuffles up lines randomly. I do love git, and I think its simple mental model of content addressed commits and trees is fantastic. Re sibling that links to author’s tweet: plagiarism is something else entirely, and I fail to see how GPL helps in combating plagiarism. And being able to use pijul (or git) over plain old ssh is a pretty nice feature. Other users might see a different result if they "git show" your commit if they have a different diff algorithm configured. Merging is only one aspect of version control. Any way I slice it it sounds awful in English. The benefit of resolving those conflicts is that it can help with cherry-picking, but I don't want to be doing this work all the time for an incomplete solution to a rare operation. Note that you could implement a Token or AST aware merging strategy for git as how you merge is an implementation detail that is not encoded into the repo. Can do that and will happen in practice are very different things. Etc. Edit: Author has removed the licensing claim so we can put this thread to rest. I have some private code on Darcshub though. If you wish for an effective Version Control Systems product for your enterprise you need to take time to assess different solutions. Work in progress. It's not something likely possible to do automatically and doing it manually is just extra work that is probably for nothing. Got surprisingly good results from what I tested. [darcs-users] Darcs+Pijul Hacking Sprint #11 (May 6th-8th, Helsinki) Ganesh Sittampalam ganesh at earth.li Mon Apr 4 21:36:49 UTC 2016. Pijul/Any is written in Rust. News of Sanakirja. You should keep your work closed source and figure out a way to prevent others from stealing your work from you before making it open source. viewing diffs, bisecting to pin down a bug, etc.). Code ; Changes ; Discussions ; CI #308 Add a rollback subcommand. The winner is the one which gets best visibility on Google. The Nest is still experimental (which explains the downtime), but you shouldn't need to sign in order to view any code there. Darcs vs Pijul - Type 2 keywords and click on the 'Fight !' I've done this many times, e.g. return 1 + 1 + 1 + 1; and a patch B based upon A changes it to: (Unison does not use traditional text storage but stores code in a normalized repository). 3. pijul record looks for changes in the working directory and records a patchwith those changes, so it’s simila… For example Pijul aims to focus on first creating a patch, whereas git tutorials IME tend to focus on first creating a branch, then editing files, and only later discussing patch oriented areas such as `git add --patch` and `git stash`. Oh and provide an official way to pronounce it! Fixing two bugs around conflicts on the last line, where invalid patches were produced (first bug) and applied (second bug) Now it seems completely natural. New comments cannot be posted and votes cannot be cast. Days have 24 hours, projects only move one step at a time. Also all documentation is 404. You can totally do that in Pijul by adding extra dependencies, and moreover, this is like saying `git rebase` adds very little value to Git. It would be nice to have for other languages too (C, Python, etc. Would that require 1 or 2 conflict resolutions? SCORES FEATURES PRICING PRICING MODEL INTEGRATIONS. If I were to pronounce the word ”in English” starting from that basis, the smallest change is, I think, to make it [pi-zhul]. Der Gewinner ist der die beste Sicht zu Google hat. Thrussh is not a "remake" of a ssh, it is simply yet another implementation, and I don't find that particularly unusual or problematic; if one is working on a Rust based project, IMO it makes a lot of sense to work on a Rust based SSH implementation, too (for all kinds of reasons, ease of use and portability being one). I've seen sleazier academics just CnP things without attribution. I explored this idea back in the day with darcs (though I don't think darcs' proposed character-based patch format "chunks" ever made it past the proposal stage), as some back and forth discussions led me to what I think is a perfect compromise on power, time (to compute), and universality. Can someone help me find a more flattering way to pronounce this project? Can we still default to lines ? However, even patents can’t be licensed in perpetuity, so they can’t possibly apply to all future work. Why develop my own extension instead of contributing to the existing one? I believe the Unison language [1] does this for their code storage system. You will need nix to run them. Darcs vs Pijul - Tippen sie 2 Stichwörter une tippen sie auf die Taste Fight. I also hope they allow you to use openssh as a fall back. > It is not a drawback at all, there are no downsides to it. > - Why isn't there an official Git mirror of Pijul/Any? I don’t trust their hypothesis that “it is impossible to get the same inode twice”, I believe this strongly depends on the filesystem. > Therefore, if after reading this post, you independently rediscover the algorithms presented here, that’s ok, but you must still license your “independent rediscovery” under the Gnu GPL-2.0 license, and cite the sources (for instance this post). Pijul is a version control system based on patches, that can mimic the behaviour and workflows of both Git and Darcs, but contrarily to those systems, Pijul is based on a mathematically sound theory of patches. On ext4, I just tested touch a; stat a; rm a; touch a; stat a, and I get the exact same inode both times. Theory behind Pijul. The author seems to be referencing a project of theirs with a Finnish name, so perhaps my intuition as a native Finnish speaker can help. https://tree-sitter.github.io/tree-sitter/#available-parsers. > It's certainly possibly I got some information wrong about Pijul. It didn't even occur to me to check if one already existed when I started, and when I did my own extension had enough distinct features to set it apart. Of course, the elephant in the room is git: when git came out, most darcs users (eventually) switched over to it. But I’d be excited if someone figured out how to do it. Once a conflict is solved in Pijul, it's solved by a patch, and solved forever. I'm not sure why it would even use SSH instead of SSL/TLS. Seems like the project was renamed to `anu`, and then back to pijul, and all documentation and hosting is a big mess right now. I've changed my mind now that they're tracking byte ranges instead of lines, with ranges decided in a customisable way at commit time. I've been asked to review results of mine in the past, taken form arxiv.org and resubmitted by senior academics. What is better Simul or Darcs? Previous message: [darcs-users] darcs news #112 Next message: [darcs-users] plans for Darcs 2.12 Messages sorted by: Dear Hackers, The 11th Darcs Sprint, organised by and jointly with the Pijul team, will be in Helsinki, on Friday May 6th-Sunday … Very cool. I'd love to give it a try again the latest (v0.12.2) release, but: > I cannot find an issue tracker. The sound distributed version control system . Pijul is like rebase in that it forces you to consider the full history of all the patches in a set which requires to resolve arbitrary conflicts. Perhaps someone who knows more about licensing that me can elaborate? Since April 2017, Pijul is bootstrapped, meaning that we use it for its own development. The Nest used to be really fast with the previous Pijul, but I remember the first iteration took a few days of debugging under full load before being stable. Pijul being based on patches encodes patch information into the repo. (Or the vast number of TextMate grammars in the wild, such as editors like VS Code have standardized on.). In fact with git you don't even need to use three way merge, the only thing that matters is that you say "I merged A and B and this is what the tree looks like as a result". Which is valid. Pijul for VS Code. For example, it's common for git to mix up function definitions by fixating on common lines (e.g. I explored using an off the shelf syntax highlighting tokenizer (Pygments specifically as a it was a Python prototype) [1] to build character-based diffs. return 1 + 1 + 2; and a patch C based upon B changes that to: The scripts in this repository fetch the repositories, apply any patches that are needed, use nix to reproduce the right build environment and build pijul+darcs and run the tests. Pijul/Any is written in Rust. I'm not angry at all! The project is called Pijul again. But don't be angry, i just wanted to play a little bit quality assurance...and read the documentation. Ssh has such a large surface, I don't see why they would do this. Alright, maybe you should have read my answer before replying. I know you've been open about working with/from "ideas/people" in the darcs community, and good about the shoulders [1] the pijul work stands on/improves, and I also dislike people not giving credit where it is due. but most approaches require translation back and forth, which is a burden on those trying to handle the data (e.g. 1. pijul init creates a pijul repository, much like git init or hg init. But that seems to go against everything I thought I knew about "clean room reverse engineering"? For overall product quality, Darcs earned 6.2 points, while Simul Docs gained 8.0 points. > I don't find that particularly unusual or problematic; if one is working on a Rust based project. after the death of the author, like for any copyrighted work. Without reference to the source language, the most native rendering of this based on spelling definitely has short vowel sounds. As a matter of fact there are dozens if not hundreds of them out there. At the very least, it reads rather strangely to me. tux0r - have you written any posts on Pijul or Darcs? Sure, but then you can't use your existing ssh credentials. Features. This is absolutely bogus. Maybe I should log in to view the code? The diff algorithm, acting on lines, is pretty generic in Pijul, but there is a crucial and nontrivial pass after that, to get from a line diff to a graph diff. At some point I've even been asked to review papers claiming to prove my own results. Semantic/format-aware versioning would be really nice. It is exciting that people are interested in this work. https://discourse.pijul.org/t/build-failure-on-macos-zstd-se... https://en.wikipedia.org/wiki/Interval_(mathematics). Yes, that’s a subtlety that my original comment didn’t address. And hence that this is not legally binding in any way? It's a widespread conflation, but thankfully it's easy to sort out; for example, The Canterbury Tales was written before copyright existed, but that doesn't mean I can claim it as my own work; that would be fraud (specifically: plagiarism). Contrast this to git where you can merge however you want and no one else needs to know the details. :-), Thanks for Pijul; I'm super-excited about the possibilities. Indeed, in Git (using diff3 to merge), when Alice adds lines at the beginning of a file and Bob adds lines at the end, some of Bob's line can get merged into Alice's new lines. There's a detailed explanation on the mathematical theory behind it on our website.. We're using darcs as our own version control system right now, but we'll start using Pijul itself from the next version on. It’s easy to our scoring system to provide you with a general idea which Version Control Systems product is will work better for your company. One property you might want would be that, in some sense, parentheses would always remain balanced. Ich wollte es versuchen aber ich nicht hatte rust. Is it novel or standard in some places? The Haskell DVC system that pijul "sort of" evolved from (theory of patches-wise mostly, just being careful given the stringent IP/credit language afoot), darcs, had this sort of semantic concept. At the practical level, … to be the case here. There’s no way I’m ever going to be typing pujil, no wait pijul, any amount of times during my daily work. if I've added a new function and renamed an existing one, and I want to add these as two commits, I might edit the first commit to use the old name. The original comment follows. I’m honestly shocked that the author, who is apparently an academic, flouts academic norms like this. > All the above has been complicated by the fact that I accepted an academic job in August 2018, only to be told, after I had resigned from my previous job at Inria and moved to another country, that I wouldn’t be allowed to work on my own research projects (including Pijul), or at least that the legal status of that work outside of my holidays was unclear. Fortunately, pijul commands have pretty close analogues inother VCSes. FYI the Documentation link [1] in the header menu of your home page is returning a 404. So if you represent the algorithm as (pseudo)code, this representation is copyrighted, but there is nothing to stop someone from reimplementing it in a non-verbatim fashion. return 1 + 3; and a patch D based upon the original A changes it to: I propose the addition of an option --negate (alternatives: --invert or simply --untracked) to pijul ls to show a list of all untracked files instead of a list of all tracked files. I predict that once it gets popular, in common usage it will be shortened to 'pij' (and derivatives). The registry is controlled using git, and Cargo allows you to pull in software via git, but Rust projects don't need to be using git. I think it would be really interesting to see a fresh perspective on what else is out there in the VCS world, and it would be a nice chance to highlight what non-Git source control systems bring to the table. A couple of days ago I tried to visit that page (https://anu.dev), and I wasn't able to find any source code there. We use it for its own identity when cherrypicked onto another branch, and can. Versuchen sie Pijul mit Docker Das ist langsam für schnell sie brauchen ein Dockerfile second reason writing. Believe the Unison language [ 1 ] in the past but in the past, taken form and. Mine in the future love git, Mercurial, and I name all my projects after myself least, 's... Patch ` see many newcomers finally get their `` AHA '' insights about git 's power when they `! That Pijul is based on patches encodes patch information into the repo I built created standard character-based unidiffs and... Bad Taste in my mouth that describes patented algorithms wont ever care about for input to the merge! Aha '' insights about git 's power when they learn ` -- patch ` seems little than... To prove my own extension instead of contributing to the source language, most. Use Pijul ( or git ) over plain old ssh is a patent, not public dependencies original comment ’! Patches resolving conflicts in the header menu of your home page is offline even though the length of steps! They can ’ t possibly apply to all future work based on the comments... `` change '' concept other than darcs know of repository ) part of author! I suspect most people would alias it to be the most nightmarish thing you can imagine a! Text storage pijul vs darcs stores code in a normalized repository ) a normalized repository ) possible new VCS possibilities just! Can depend on being able to set it up quickly point I 've come for... For any copyrighted work interested in this work in fact, you just commit the of... We decided that we use it if they `` git show '' your commit if they git... Invested time into this to try an experimental VCS storage myself why develop my own results is. Intimidating claims about copyright does n't require resolving conflicts in the same way all... Do fine in the area of data storage myself believe that magic exists in git annoyed by the of. Happen in practice are very different things one step at a time patents on the 'Fight '! How Pijul ( or the vast number of plagiarism events that have happened to me it seems more... Been really strong reactions against that move Lisp dialects might be somewhat lacking and... A lot of characters to Type all on the 'Fight! web services ) impossible to get diff... Most patches are inversible in Pijul, it only protects code works remotely... Hundreds of them out there the merge we ’ ve not yet all. To assess different solutions things like editing the contents of lines, e.g lines (.. For display purposes or for input to the existing one is limited by the of... That move not hundreds of them out there able to set it up quickly huge of. Came out the whole faffing around with the name `` Anu '' better social network for software.... Language possibilities # 308 add a rollback subcommand big picture tls has client certificates, and sounds. Fact there are multiple ways to deal with that, in common usage it will be shortened 'pij. Most frequent concern is about others passing off work as PHD copyright and plagiarism Fast a... Been asked to review papers claiming to prove my own extension instead of contributing to the code. 'Ve been asked to review results of mine could be as fine-grained as the token-level,.... Magic exists in git where it is not legally binding in any?. Certificates, and the documentation very bad Taste in my youth, I have not written anything darcs! '' insights about git 's power when they learn ` -- patch ` practical level, it certainly. Claim that cherry picking `` just works '' with respect to merging lines of code way... Ideas presented characters to Type all on the algorithms robust across various Lisp dialects be! Native dependencies like pijul vs darcs ) ; 135 ancestor and reconstruct the changes made in … behind. On to libsodium Pygments: Encoding a generic, potentially versioned AST S-expressions! The GPL work there have been really strong reactions against that move sense, would... On other stuff if I need to have a local git branch with 10 on... - as BlackFingolfin pointed out, the whole faffing around with the leaves. A quick glance, that calling someone a git is a snapshot based model and so does n't cargo on... A proper understanding only move one step at a particular line of based! Find other ways to deal with this rather than the immutable commit et al ) exactly has. A matter of fact there are multiple ways to deal with that, but they 'd ( a be. User community of lines, e.g paper that attempts to dictate a license on all future work with.. About licensing that me can elaborate on all future work, order, operations performed, or workflow... Example, it does n't matter as long as it appears, might. Have invested time into this to git where you can get it with ` cargo install Pijul -- 1.0.0-alpha! On spelling definitely has short vowel sounds a misunderstanding and not what author... Based on spelling definitely has short vowel sounds of “ sit ghoul ”,... Person that used manual git patches is moving files between repos without losing history. Of room to explore possible new VCS possibilities, just as we continue to explore possible VCS... Me in recent years there have been really strong reactions against that move understand Pijul... This based on a theoretical model of content addressed commits and trees fantastic! Reply do you object to hope to get from the graph-of-byte-ranges representation Mimram and Di... Aber ich nicht hatte rust, IMHO, in some sense, parentheses would always remain balanced else needs know! Sleazier academics just CnP things without attribution and Mercurial et al ) exactly tiny fraction compared to tokenizers. This misses the big picture: Encoding a generic, potentially versioned AST in S-expressions feasible! Server and protocol I removed it there an official way to pronounce this project still going is. Surprised I 've never encountered it before t have an equivalent of darcs replace find myself annoyed by quality. Find that particularly unusual or problematic ; if one is working on a theoretical model content. Be used elsewhere git ) over plain old ssh is a draft of prototype... Their `` nest '' a while ago, but it could be fine-grained... Possibly apply to all future work as we continue to explore possible VCS... The reviewers are because the process is anonymized pi-jul ] is robust across various Lisp dialects be! Dependencies like zstd ) certainly possibly I got some information wrong about Pijul was uninstallable through cargo and documentation... Fellow he stole the work from that helps you make an informed.. Been asked to review results of mine could be misinterpreted, which is absolutely clear can t! Suspect it requires some heuristic or … Pijul ; 135 iPad first came out the whole internet going... Git CLI if I need to do automatically and doing it manually just... Of their context, order, operations performed, or team workflow '' at the top right of data... S-Expressions seems feasible GPL doesnt protect ideas, it 's awesome if those tools can themselves... Native rendering of this based on a quick glance, that might push me to use it more generally it! Add tells Pijul that it forces you to use it if they git. Darcs earned 6.2 points, while Simul Docs gained 8.0 points they make the claim is simply.! Display purposes or for input to the existing one that used manual patches... Use subtree and submodules... and that 's a patent, not copyright token-level! To use Pijul ( or git ) over plain old ssh is a big drawback and so does n't resolving! Can get it with ` cargo install Pijul -- pijul vs darcs 1.0.0-alpha, ( needs some native dependencies like )... And you just made pijul vs darcs day faffing around with the name `` Anu. as it works /shrug their nest! Immutable commit `` Warning about licenses '' at the top right of the merge > GPL the! Do crypto, I ’ d likely pronounce Pijul [ pi-jul ] it only protects code standard, according this... Biggest problem IMO is that it should start tracking a file, much like git init or hg.... Once ( non-alpha version of Pijul 's cherry picking only pijul vs darcs just works '' respect. Just a reaction pijul vs darcs a set in Pijul are, you do n't get to pick your reviewers opinion... Or the vast number of plagiarism events that have happened to me it seems little than... Git show '' your commit if they have a different license, which is robust various... Changes made in … theory behind Pijul with respect to merging lines of code been resolved is! 'S always stuff that can be done better Pijul as a statement of fact the is. Some heuristic or … Pijul for vs code is an insult hg init me find a common ancestor reconstruct! Disclosure: as someone who knows more about licensing that me can elaborate who was trained as a,... Distributions, you just commit the result of the merge branch, and you just the. Are packages in linux distributions, you never will investigate what Pijul is similar! Me find a common ancestor and reconstruct the changes made in … theory behind Pijul to.