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…	9	816	February 22, 2018
About the Development category	1	218	June 1, 2017
Is having `replace` a sensible idea?	3	100	September 10, 2020
Patch based version control	8	261	July 23, 2020
Incorporating discussions into the repo itself	11	1059	July 20, 2020
Suggestion: change executable name to `pj`	11	881	July 15, 2020
Git compatibility	11	1138	July 15, 2020
Calling branches "branches" is misleading	14	1019	July 12, 2020
Building pijul for target x86_64-pc-windows-msvc with vcpkg	4	134	June 11, 2020
Writing the patch description from an editor	12	854	May 10, 2020
Base 58 ⇒ Base 32	7	887	January 9, 2020
AST-level diffs and merges	12	2028	December 24, 2019
Random Talks and Thoughts	20	1256	December 24, 2019
Idea: privacy-sensitive way to link commits to author in The Nest	6	310	November 20, 2019
Development plans	1	352	August 22, 2019
Pijul is super slow when compared to git	3	723	August 19, 2019
Bug when importing LLVM into a Pijul repository	1	204	August 12, 2019
Pijul Bug with Unrecording?	3	277	May 26, 2019
Any plans to make tags first-class things?	4	444	May 12, 2019
Building a git-ssb like remote for ssb	1	231	April 4, 2019
Using rustfmt systemically	30	1464	March 14, 2019
Ask before proceeding when unrecording a patch with dependencies	9	345	February 23, 2019
[SOLVED] KeyError fix	3	225	February 23, 2019
Bad performance	17	1447	December 11, 2018
Redmine integration	2	286	October 19, 2018
Patching patches	20	1321	September 12, 2018
A composable pijul user interface? (brainstorm)	21	2713	May 2, 2018
Benchmarking pijul	2	351	April 25, 2018
Last adjustments before Pijul 0.10	3	331	April 20, 2018
Semantics of "missing contexts" conflicts	7	467	March 13, 2018

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…