Development

Warning: Patch hash format changed (breaking change) (9)

The patch hashes are currently base64-encodings of the SHA2-512 of the patch as written in binary. This is not optimal, especially when we need to copy-paste hashes (which does not happen very often for me). I was thin…

About the Development category (1)

Ask before proceeding when unrecording a patch with dependencies (6)

Calling branches "branches" is misleading (1)

Suggestion: change executable name to `pj` (6)

[SOLVED] KeyError fix (2)

Bad performance (17)

Incorporating discussions into the repo itself (6)

Redmine integration (2)

Patching patches (20)

Using rustfmt systemically ( 2 ) (28)

Random Talks and Thoughts (19)

Git compatibility (8)

AST-level diffs and merges (8)

A composable pijul user interface? (brainstorm) ( 2 ) (21)

Benchmarking pijul (2)

Last adjustments before Pijul 0.10 (3)

Semantics of "missing contexts" conflicts (7)

Lots of conflicts (7)

Getting ready for 0.9 (4)

Prepare the release of pijul-0.8 (10)

Writing the patch description from an editor (8)

Heads-up: recent bugs with conflicts and with the Nest (6)

Pre-record hook (7)

Request for comments: Listing files with conflicts in `pijul status` (14)

About warning: using `clone` on a `Copy` type [clone_on_copy] (5)

Spontaneous (non-)branching vs. tree-style branches (10)

Official Reporitories and Official History (19)

Prepare pijul-0.7.0 ( 2 ) (21)

A safe API for sanakirja (5)