Collapse None and Some(false) variants of force_cache since they are treated the same
Dependencies
- [2]
DO2Y5TY5Tag synchronisation - [3]
FKUPWOP7Removing the `--tag` option to push and pull - [4]
IVLLXQ5ZImproved push/pull reporting - [5]
YD7QFAD7Simplifying pijul::remote::PushDelta - [6]
OYN2YVPACreate `pijul_remote` crate - [7]
TCFJMFFEUsing state_from_prefix and hash_from_prefix on remotes to complete (or find) hashes and states - [*]
SXEYMYF7Fixing the bad changes in history (unfortunately, by rebooting).
Change contents
- replacement in pijul-remote/src/lib.rs at line 706
force_cache: Option<bool>,force_cache: bool, - replacement in pijul-remote/src/lib.rs at line 772
let should_cache = if let Some(true) = force_cache {true} else {remote_unrecs.is_empty()};let should_cache = force_cache || remote_unrecs.is_empty(); - replacement in pijul/src/commands/pushpull.rs at line 477
Some(self.force_cache),self.force_cache, - edit in pijul/src/commands/pushpull.rs at line 649
let force_cache = if self.force_cache {Some(self.force_cache)} else {None}; - replacement in pijul/src/commands/pushpull.rs at line 654
force_cache,self.force_cache,