|
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
|
February 22, 2018
|
|
About the Development category
|
1
|
June 1, 2017
|
|
Base 58 ⇒ Base 32
|
3
|
May 29, 2019
|
|
Pijul Bug with Unrecording?
|
3
|
May 26, 2019
|
|
Any plans to make tags first-class things?
|
4
|
May 12, 2019
|
|
Building a git-ssb like remote for ssb
|
1
|
April 4, 2019
|
|
Using rustfmt systemically
|
30
|
March 14, 2019
|
|
Incorporating discussions into the repo itself
|
8
|
March 11, 2019
|
|
Calling branches "branches" is misleading
|
9
|
March 4, 2019
|
|
AST-level diffs and merges
|
11
|
March 4, 2019
|
|
Ask before proceeding when unrecording a patch with dependencies
|
9
|
February 23, 2019
|
|
[SOLVED] KeyError fix
|
3
|
February 23, 2019
|
|
Suggestion: change executable name to `pj`
|
6
|
January 25, 2019
|
|
Bad performance
|
17
|
December 11, 2018
|
|
Redmine integration
|
2
|
October 19, 2018
|
|
Patching patches
|
20
|
September 12, 2018
|
|
Random Talks and Thoughts
|
19
|
September 5, 2018
|
|
Git compatibility
|
8
|
May 16, 2018
|
|
A composable pijul user interface? (brainstorm)
|
21
|
May 2, 2018
|
|
Benchmarking pijul
|
2
|
April 25, 2018
|
|
Last adjustments before Pijul 0.10
|
3
|
April 20, 2018
|
|
Semantics of "missing contexts" conflicts
|
7
|
March 13, 2018
|
|
Lots of conflicts
|
7
|
February 20, 2018
|
|
Getting ready for 0.9
|
4
|
January 11, 2018
|
|
Prepare the release of pijul-0.8
|
10
|
December 30, 2017
|
|
Writing the patch description from an editor
|
8
|
September 21, 2017
|
|
Heads-up: recent bugs with conflicts and with the Nest
|
6
|
August 31, 2017
|
|
Pre-record hook
|
7
|
August 28, 2017
|
|
Request for comments: Listing files with conflicts in `pijul status`
|
14
|
August 26, 2017
|
|
About warning: using `clone` on a `Copy` type [clone_on_copy]
|
5
|
August 14, 2017
|