On 05/12/2017 06:59 PM, Dustin Mitchell wrote:
Yep, this caused problems in automation (we ended up setting
I_PREFER_A_SUBOPTIMAL_MERCURIAL_EXPERIENCE_THANK_YOu or whatever the
env var was). I agree that a quick warn-and-continue would be fine.
Especially for git users. ;-)
Speaking of nagging that can be off putting, I have to admit I almost
never run mach bootstrap because it forces me make a decision about how
I want mercurial to be updated which I don't use. The only times I run
mach bootstrap are on fresh installs of OSes and past that, I stick to
manually updating my tools when things that depend on them break.
Dustin
2017-05-12 15:23 GMT-04:00 Eric Rahm <er...@mozilla.com>:
Didn't it somehow cause builds to fail? A gentle reminder is probably fine.
TBH I'd be fine if it auto-updated but maybe I'm in the minority.
On Fri, May 12, 2017 at 11:34 AM, Ted Mielczarek <t...@mielczarek.org> wrote:
On Fri, May 12, 2017, at 10:45 AM, Sylvestre Ledru wrote:
Would it be possible to add a check like:
"You haven't updated your local configuration since XX days, please
consider running
mach bootstrap ?"
We've had mach produce nag messages like that in the past and they have
been universally disliked, FWIW.
-Ted
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
