Overview
| Comment: | When suppressing variables at execute time be sure to actually unset them in the current environment. WARNING: This may be a wrong-headed strategy. Does suppressing vars mean megatest should not clobber or override or does it mean that it should unset? |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | v1.65 |
| Files: | files | file ages | folders |
| SHA1: |
2454028ce7b5efdf6e1c7c467846d322 |
| User & Date: | mrwellan on 2019-11-19 12:40:53 |
| Other Links: | branch diff | manifest | tags |
Context
|
2019-11-21
| ||
| 03:22 | Added beginnings of multi-level glob check-in: e22603e687 user: matt tags: v1.65 | |
|
2019-11-19
| ||
| 12:40 | When suppressing variables at execute time be sure to actually unset them in the current environment. WARNING: This may be a wrong-headed strategy. Does suppressing vars mean megatest should not clobber or override or does it mean that it should unset? check-in: 2454028ce7 user: mrwellan tags: v1.65 | |
|
2019-11-14
| ||
| 10:20 | Updated megatest version to 1.6538. check-in: c165b41110 user: mmgraham tags: v1.65, v1.6538 | |
Changes
Modified launch.scm from [bce9848f66] to [0962cf8b36]. [diff]