| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This has been stolen from gnome-continuous default settings:
https://git.gnome.org/browse/gnome-continuous/tree/src/ostree-build-compile-one#n96
Change-Id: I01a88123f29d1a79683a10973a5597aab3b7cf5f
|
|
|
|
| |
Change-Id: I7248dd34529eaaa8e92fb811d60146678ea5acd3
|
|
|
|
| |
Change-Id: Id06c0e6688764310962d67268d09c3697b734634
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
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
|