Re: [lldb-dev] [llvm-dev] [cfe-dev] [Github] RFC: linear history vs merge commits

2019-02-04 Thread Jameson Nash via lldb-dev
> The way it decides that there are "outdated comments" and that those comments should be hard to does not win it any points in my book (Hubert Tong) IIUC, Github has recently changed this, and is now more like Phabricator. (in that it now seems to add a mark to say the diff is likely outdated,

Re: [lldb-dev] [llvm-dev] [cfe-dev] [Github] RFC: linear history vs merge commits

2019-02-01 Thread Tom Stellard via lldb-dev
On 01/31/2019 09:51 AM, Roman Lebedev via llvm-dev wrote: > On Thu, Jan 31, 2019 at 8:29 PM David Greene via cfe-dev > wrote: >> >> Mehdi AMINI writes: >> >>> What is the practical plan to enforce the lack of merges? When we >>> looked into this GitHub would not support this unless also forcing

Re: [lldb-dev] [llvm-dev] [cfe-dev] [Github] RFC: linear history vs merge commits

2019-02-01 Thread Tom Stellard via lldb-dev
On 01/30/2019 10:53 PM, Mehdi AMINI via llvm-dev wrote: > > > On Wed, Jan 30, 2019 at 1:19 PM Eric Christopher via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > On Wed, Jan 30, 2019 at 12:42 PM David Greene via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > > >

Re: [lldb-dev] [llvm-dev] [cfe-dev] [Github] RFC: linear history vs merge commits

2019-01-31 Thread Jeremy Lakeman via lldb-dev
https://help.github.com/articles/checking-out-pull-requests-locally/ Script a bot to scrape the patches and post to phabricator? On Fri, 1 Feb 2019 at 04:22, Roman Lebedev via llvm-dev < llvm-...@lists.llvm.org> wrote: > On Thu, Jan 31, 2019 at 8:29 PM David Greene via cfe-dev > wrote: > > > >