diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-07-05 00:53:12 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-07-05 00:53:12 -0700 |
commit | f28f2636c6707e1a33bebacafd0486f4965978ea (patch) | |
tree | eba4edbcbf6cd4ad1e14b9629613003bf224c3f1 /010vm.cc | |
parent | 7e85c3362ce7e34165d90695fb86d3e421837fe8 (diff) | |
download | mu-f28f2636c6707e1a33bebacafd0486f4965978ea.tar.gz |
3101 - purge .traces/ dir from repo history
I'd been toying with this idea for some time now given how large the repo had been growing. The final straw was noticing that people cloning the repo were having to wait *5 minutes*! That's not good, particularly for a project with 'tiny' in its description. After purging .traces/ clone time drops to 7 seconds in my tests. Major issue: some commits refer to .traces/ but don't really change anything there. That could get confusing :/ Minor issues: a) I've linked inside commits on GitHub like a half-dozen times online or over email. Those links are now liable to eventually break. (I seem to recall GitHub keeps them around as long as they get used at least once every 60 days, or something like that.) b) Numbering of commits is messed up because some commits only had changes to the .traces/ sub-directory.
Diffstat (limited to '010vm.cc')
-rw-r--r-- | 010vm.cc | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/010vm.cc b/010vm.cc index 8599b74d..198244e4 100644 --- a/010vm.cc +++ b/010vm.cc @@ -434,8 +434,7 @@ void dump_memory() { } //:: Helpers for converting various values to string -//: Use to_string() in trace(), and try to avoid relying on unstable codes that -//: will perturb .traces/ from commit to commit. +//: Use to_string() in trace(), and try to keep it stable from run to run. //: Use debug_string() while debugging, and throw everything into it. //: Use inspect() only for emitting a canonical format that can be parsed back //: into the value. |