check in
authorM. Taylor Saotome-Westlake <[email protected]>
Wed, 10 Jan 2018 17:46:10 +0000 (09:46 -0800)
committerM. Taylor Saotome-Westlake <[email protected]>
Wed, 10 Jan 2018 17:46:23 +0000 (09:46 -0800)
commit9a53e3e62924cdc08e6c5f1706c38ad40530750c
treee8a67920be686e14e322bb5a11e156f859a2c99d
parentec76aeb5802d53e1272fb57c473f05feb5e1cdb8
check in

My commit-discipline when writing is much weaker than when coding—as you've
noticed, I'll often make little changes to many files, and then lump them into
one commit under the message "check in". In this case, I want to start my
writing day with a clean repo state, so that the git-wordcount (new command I
wrote, like it sounds) of my next "drafting 'The Categories ...'" commit is
more localized in time.
content/drafts/the-categories-were-made-for-man-in-order-to-make-predictions.md
notes/speculative_scheduling.txt