On Tue, Jun 16, 2020 at 12:13:31PM -0400, Santiago Torres Arias wrote: > > What if we work on making this configurable for now, but stick with the > > legacy name until we introduce breaking sha1 changes? Almost everything > > will need to retool for those anyway (and all documentation rewritten), > > so it is reasonable to bundle these changes to happen at the same time. > > I wonder if allowing the buildsystem to set this default value would be > a wortwhile stepping stone. This way we can test things in different > ecosystems. If you mean allowing "make DEFAULT_BRANCH_NAME=foo", that seems reasonable to me. Though the tests likely wouldn't run in that case (unless we are planning to leave the test-environment-munging bit in place forever, I suppose). -Peff
