head	1.1;
access;
symbols
	pkgsrc-2026Q1:1.1.0.28
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.26
	pkgsrc-2025Q4-base:1.1
	pkgsrc-2025Q3:1.1.0.24
	pkgsrc-2025Q3-base:1.1
	pkgsrc-2025Q2:1.1.0.22
	pkgsrc-2025Q2-base:1.1
	pkgsrc-2025Q1:1.1.0.20
	pkgsrc-2025Q1-base:1.1
	pkgsrc-2024Q4:1.1.0.18
	pkgsrc-2024Q4-base:1.1
	pkgsrc-2024Q3:1.1.0.16
	pkgsrc-2024Q3-base:1.1
	pkgsrc-2024Q2:1.1.0.14
	pkgsrc-2024Q2-base:1.1
	pkgsrc-2024Q1:1.1.0.12
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.10
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.8
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.6
	pkgsrc-2023Q2-base:1.1
	pkgsrc-2023Q1:1.1.0.4
	pkgsrc-2023Q1-base:1.1
	pkgsrc-2022Q4:1.1.0.2
	pkgsrc-2022Q4-base:1.1;
locks; strict;
comment	@# @;


1.1
date	2022.12.13.22.10.14;	author nikita;	state Exp;
branches;
next	;
commitid	psDqIlTnU4RZIr5E;


desc
@@


1.1
log
@devel/pijul: import pijul-1.0.0.beta2

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.

Pijul was started out of frustration that no version control system
was at the same time fast and sound:

- Git has non-associative merges, which might lead to security problems.
  Concretely, this means that the commits you merge might not be the same as
  the ones you review and test.

- Handling of conflicts: Pijul has an explicit internal representation of
  conflicts, a rock-solid theory of how they behave, and super-fast data
  structures to handle them.

- Speed! The complexity of Pijul is low in all cases, whereas previous
  attempts to build a mathematically sound distributed version control
  system had huge worst-case complexities. The use of Rust
  additionally yields a blazingly fast implementation.
@
text
@@@comment $NetBSD$
bin/pijul
@