| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | DEFAULTS: Set some typical default for the autotools build system | Javier Jardón | 2016-02-16 | 1 | -0/+3 |
| | | | | | Change-Id: I7248dd34529eaaa8e92fb811d60146678ea5acd3 | ||||
| * | Add new python3-distutils build system | Javier Jardón | 2016-02-12 | 1 | -0/+10 |
| | | | | | Change-Id: Id06c0e6688764310962d67268d09c3697b734634 | ||||
| * | Fix migration to VERSION 7. | Pedro Alvarez | 2015-11-23 | 1 | -0/+2 |
| | | | | | | | | | | | | The migration script was updated after the commit 948454110a3d6af4fedc0d292fcc1e48475cc7c5 was submitted for review. This commit updates DEFAULTS to what the migration script actually generates. Change-Id: I9590f15aba67e32086d2fae18a88f5ccd8473263 | ||||
| * | Migrate to definitions format version 7: add a DEFAULTS file | Sam Thursfield | 2015-11-21 | 1 | -0/+197 |
| This is the DEFAULTS file embedded in migrations/007-defaults-in-definitions.py, which is exactly the settings that are also built into Morph. I expect the DEFAULTS file used in definitions.git to change over time, but we don't need to keep the one in migrations/007-defaults-in-definitions.py in sync. People who have forked definitions and want to keep their DEFAULTS in line with ours should use `git merge`. So it might seem like migrations/007-defaults-in-definitions script is not useful (`git merge` could have handled adding DEFAULTS, too), but we need to have a migration for *every* version so that you can easily go from V1 to V10, or whatever, without having to do a 'git merge' from definitions.git first. Change-Id: Idf19c31da013eddcf2e1f165086e697ca1805498 | |||||
 |
index : baserock/baserock/definitions.git | |
| gitlab.com: baserock/definitions.git |
| summaryrefslogtreecommitdiff |