Re: [lldb-dev] [llvm-dev] [cfe-dev] GitHub anyone?

2016-06-01 Thread Jim Rowan via lldb-dev
+1 We use git exclusively within QC, so this looks like simplification to us. There was mention early in the thread of continuing to enforce linear history; that’s important to our internal integration machinery. We do currently use the git-svn-id as a key for some of our internal processes

Re: [lldb-dev] [llvm-dev] [cfe-dev] What version comes after 3.9? (Was: [3.9 Release] Release plan and call for testers)

2016-06-27 Thread Jim Rowan via lldb-dev
On Jun 27, 2016, at 9:57 PM, Chris Lattner via llvm-dev wrote: > > I continue to think that 3.10 is the least defensible option out there. I agree, given that there isn’t a concurrent agreement that we want to define and conform to a semantic versioning scheme — and that agreement not only

Re: [lldb-dev] [llvm-dev] [cfe-dev] Sequential ID Git hook

2016-06-30 Thread Jim Rowan via lldb-dev
On Jun 30, 2016, at 2:25 PM, Robinson, Paul via llvm-dev wrote: (talking about lots of tags) > I don't know that it really scales well when you > are talking about (long term) hundreds of thousands of them. I can say from experience that it does not scale well.After some time, everyone w

Re: [lldb-dev] [llvm-dev] [cfe-dev] FYI: Landing the initial draft for an LLVM Code of Conduct

2016-06-30 Thread Jim Rowan via lldb-dev
I don’t know what you meant to imply by “residual clause” — if you meant “it’s not particularly important”, then I suggest it is left out entirely. Apparently at least a few of us have interpreted it to say “the committee reserves the right to kick you out for any behaviour that violates our