1 commit

Author	SHA1	Message	Date
Takashi Kokubun	f883d6219e	Unify vm benchmark prefixes to vm_ (#3028) ... The vm1_ prefix and vm2_ had had special meaning until 820ad9cb1d and 12068aa4e9. AFAIK there's no special meaning in vm3_ prefix. As they have confused people (like "In `benchmark` what is difference between `vm1_`, `vm2_` and `vm3_`"), I'd like to remove the obsoleted prefix as we obviated that two years ago.	2020-04-13 21:37:42 -07:00

Renamed from benchmark/vm2_freezestring.yml (Browse further)