chore(git): fence the bulk so the sources can finally land
Three weeks of untracked working tree, and the reason nothing was committed is
that 'untracked' had stopped meaning anything: 957 MB of take audio and scene
mp4s sat in the same status output as three finished captain's logs, so the
whole list read as noise and got skipped as one.
Sorted by what each thing actually is, against the precedent already in this
file and in the index: mix/'s ten scripts are source and go in, mix/take94's
833 MB does not. The .js scene sketches are source, the 124 MB of rendered
mp4 is not. calibration.json and calibration.whole-mix.json are tracked, so
calibration.stem.json belongs with them; bounds_*.json is generated output
whose builder is already tracked, so it does not.
No new policy here — just applying the one written at the top of this file to
a pile that had grown too mixed to read.
the tide went out three weeks ago
and left everything on the sand together:
charts, driftwood, a gigabyte of water.
sorting is not cleaning. sorting is deciding what was ever yours.
Showing
Please
register
or
sign in
to comment