Hi,
I've got a question about how djblets.siteconfig handles changes in
the settings.py and settings_local.py files.
After upgrading to r1537 (and introducing djblets.siteconfig), as I
understand, a SiteConfiguration object has been created (and stored in
the db) that reflects the existing
This is probably a small design flaw. We're populating these settings in the
SiteConfiguration entry in the database with whatever was in settings.py,
settings_local.py or Django's default settings file, but that gives users no
way to override in settings_local.py.
Since we are populating it,
