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

2016-07-05 Thread Renato Golin via lldb-dev
On 5 Jul 2016 10:45 p.m., "Mehdi Amini" wrote: > > > > On Jul 5, 2016, at 3:44 AM, Renato Golin via llvm-dev < llvm-...@lists.llvm.org> wrote: > > > > Quick re-cap. > > > > After a few rounds, not only the "external server" proposal got > > obliterated as totally unnecessary, but the idea that we

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

2016-07-05 Thread Mehdi Amini via lldb-dev
> On Jul 5, 2016, at 3:44 AM, Renato Golin via llvm-dev > wrote: > > Quick re-cap. > > After a few rounds, not only the "external server" proposal got > obliterated as totally unnecessary, but the idea that we may even need > a hook at all is now challenged. This is not clear to me. How is t

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

2016-06-30 Thread Matthias Braun via lldb-dev
I assumed we want ids for the umbrella repository to ease bisection and having something to print as a version identifier, but do we really need them for the other repositories? I also still don't see why `git rev-list --count --all` does not work. Sure the count is only per branch, but why wou

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

2016-06-30 Thread Renato Golin via lldb-dev
On 30 June 2016 at 17:33, Reid Kleckner wrote: > Agreed, the llvm-project repository can completely take on the role of the > SQL database in Renato's proposal. Hum, doing it in a separate server was suggested by the GitHub folks, so I just assumed they can't do that in the umbrella project for s

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

2016-06-30 Thread Reid Kleckner via lldb-dev
On Thu, Jun 30, 2016 at 9:16 AM, James Y Knight via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I don't think we should do any of that. It's too complicated -- and I > don't see the reason to even do it. > > There's a need for the "llvm-project" repository -- that's been discussed > plenty -- but

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

2016-06-30 Thread James Y Knight via lldb-dev
I don't think we should do any of that. It's too complicated -- and I don't see the reason to even do it. There's a need for the "llvm-project" repository -- that's been discussed plenty -- but where does the need for a separate "id" that must be pushed into all of the sub-projects come from? This

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

2016-06-30 Thread Tom Honermann via lldb-dev
On 6/30/2016 7:43 AM, Renato Golin via llvm-dev wrote: > Given the nature of our project's repository structure, triggers in > each repository can't just update their own sequential ID (like > Gerrit) because we want a sequence in order for the whole project, not > just each component. But it's cle