Re: [lldb-dev] [llvm-dev] [cfe-dev] [Call for Volunteers] Bug triaging

2018-11-12 Thread James Henderson via lldb-dev
TLDR; Please don't just straight-up remove components based on some arbitrary numeric threshold. Just because a component doesn't get many bugs filed against it doesn't mean it isn't useful. It might just mean that the area is generally pretty stable or simply new. A good example to work with are

Re: [lldb-dev] [RFC] OS Awareness in LLDB

2018-11-12 Thread Jim Ingham via lldb-dev
> On Nov 11, 2018, at 10:30 AM, Alexander Polyakov > wrote: > > The data formatter in lldb is a subsystem that allows users to define custom > display options, the Platform is the agent that provides a way to work with a > specific platform. I agree that we need the Platform to provide the O

[lldb-dev] [monorepo] Downstream branch zipping tool available

2018-11-12 Thread David Greene via lldb-dev
Building on the great work that James Knight did on migrate-downstream-fork.py (Thanks, James!) [1], I've created a simple tool to take migrated downstream fork branches and zip them into a single history given a history containing submodule updates of subprojects [2]. With migrate-downstream-fork