Development

Topic	Replies	Views	Activity
Warning: Patch hash format changed (breaking change) 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…	8	979	February 22, 2018
About the Development category	0	269	June 1, 2017
Buildkite Source Control Integration	2	44	June 11, 2021
Using a pure Rust pager	4	370	June 10, 2021
Is having `replace` a sensible idea?	4	353	May 5, 2021
Incorporating discussions into the repo itself	11	1370	March 30, 2021
Any ideas for interpreting error messages?	3	164	March 3, 2021
Suggestion: change executable name to `pj`	16	1457	February 26, 2021
Using Pijul for a game editor	6	365	February 24, 2021
AST-level diffs and merges	12	2593	February 11, 2021
1.0.0-alpha Usage Proto Documentation	21	729	January 17, 2021
Building Alpha 22 On Windows 10	3	150	December 18, 2020
Building pijul for target x86_64-pc-windows-msvc with vcpkg	5	295	December 15, 2020
Tags, Channels, and Remotes	2	244	December 11, 2020
Support for a config subcommand	16	402	December 1, 2020
Git Attributes Filter Equivalent	1	133	November 27, 2020
1.0.0-alpha.3 Merging	14	254	November 17, 2020
Blake3 for the new hash function	10	513	October 11, 2020
Calling branches "branches" is misleading	20	1627	October 5, 2020
Git compatibility	11	1810	September 26, 2020
Patch based version control	7	537	July 23, 2020
Writing the patch description from an editor	11	1059	May 10, 2020
Base 58 ⇒ Base 32	6	1161	January 9, 2020
Random Talks and Thoughts	19	1494	December 24, 2019
Idea: privacy-sensitive way to link commits to author in The Nest	5	488	November 20, 2019
Development plans	0	431	August 22, 2019
Pijul is super slow when compared to git	2	876	August 19, 2019
Bug when importing LLVM into a Pijul repository	0	269	August 12, 2019
Pijul Bug with Unrecording?	2	352	May 26, 2019
Any plans to make tags first-class things?	3	569	May 12, 2019

Warning: Patch hash format changed (breaking change)

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…