[PATCH] traceback: allow disabling the third party extensions blaming

[Augie Fackler]

On Thu, Sep 17, 2015 at 02:43:56PM -0700, Sean Farley wrote:
>
> Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:
> >
> > I like the idea of having a different bugs report flow for big
> > deployment that have there own support layer. We still need to do
> > something about the user confusion and attempt to debug by disabling a
> > long list of extensions one by one.
>
> I have never once gotten anything useful out of the "possibly-broken"
> list because it has never been correct. In fact, I've trained myself to
> completely ignore it. I'm positive end-users are baffled as well. I like
> Pierre-Yves' direction but don't know how to proceed.

Perhaps we should list *all* the extensions with outdated or missing
testedwith lines, rather than merely picking one.

I still think pointing to extensions is of value. In general users
with unsupported extensions need to be pushed into testing their bug
without the broken extension before we hear about it.

(This code dramatically reduced noise on the bugtracker from broken
third-party extensions.)

> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> https://selenic.com/mailman/listinfo/mercurial-devel