Christopher,
Thank you for timely response. The best practice you refer to in comment #48 seems to apply to "regression"s. I don't know precisely what "regression" refers to in this context, but I assumed it meant something along the "a bug that was introduced after not existing in a previous commit". According to this assumed definition, I didn't think this was a regression. That fact, combined with the ubiquitous warnings about "negative unintended consequences," made me decide against emailing anyone else. Since the warning about such consequences still seems salient, I must ask: Is this in fact a "regression"? What is a "regression" in this context?
Christopher,
Thank you for timely response. The best practice you refer to in comment #48 seems to apply to "regression"s. I don't know precisely what "regression" refers to in this context, but I assumed it meant something along the "a bug that was introduced after not existing in a previous commit". According to this assumed definition, I didn't think this was a regression. That fact, combined with the ubiquitous warnings about "negative unintended consequences," made me decide against emailing anyone else. Since the warning about such consequences still seems salient, I must ask: Is this in fact a "regression"? What is a "regression" in this context?