Re: [lldb-dev] [llvm-dev] Updates on SVN to GitHub migration

2018-10-22 Thread NAKAMURA Takumi via lldb-dev
James and Tom, One question. Would the monorepo be fixed and would it not be re-created after the day? I am deeply cosmetic-checking the repo. For now, I haven't found critical issues, though. Takumi On Sat, Oct 20, 2018 at 9:47 AM Tom Stellard via llvm-dev < llvm-...@lists.llvm.org> wrote: >

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc3 has been tagged

2018-09-12 Thread NAKAMURA Takumi via lldb-dev
FYI, CentOS6 RPMs are here; https://github.com/llvm-project/llvm-project-20170507/releases/tag/RELEASE_700%2Frc3 On Mon, Sep 10, 2018 at 11:13 PM Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > 7.0.0-rc3 was just tagged (from branch revision r341805)

Re: [lldb-dev] [llvm-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged

2018-08-03 Thread NAKAMURA Takumi via lldb-dev
Paul, Are you using llvm-project-20170507.git ? Regarding to release_70, I am updating it manually, due to each repo.git/release_70 might not be up-to-date. In fact, openmp.git/release_70 isn't yet. Sorry for the inconvenience. Please be patient. On Fri, Aug 3, 2018 at 10:44 PM via llvm-dev wr

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

2018-02-08 Thread NAKAMURA Takumi via lldb-dev
FYI, unofficial CentOS6 RPMs are there. https://github.com/llvm-project/llvm-project-20170507/releases/tag/release_600_rc2 On Thu, Feb 8, 2018 at 5:52 AM Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > There's been a lot of merges since rc1, and hope

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] The release branch is open; trunk is now 6.0.0

2017-07-20 Thread NAKAMURA Takumi via lldb-dev
Seems lld's release_50 has been created. Openmp's release_50 isn't there. Committing branches doesn't trigger git-svn. Release_50 will be created when someone committed something in trunk. On Fri, Jul 21, 2017 at 1:05 AM Khem Raj via llvm-dev < llvm-...@lists.llvm.org> wrote: > Hi Hans > > On We

Re: [lldb-dev] [Release-testers] [4.0 Release] Schedule and call for testers

2016-12-06 Thread NAKAMURA Takumi via lldb-dev
I hope you could branch and tag to projects atomically. Are you able? On Tue, Dec 6, 2016 at 3:26 AM Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear everyone, > > There's still plenty of time left, but I'd like to get the schedule > set before folks start disappe

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

2016-07-03 Thread NAKAMURA Takumi via lldb-dev
"git-describe -t" works also for lw tags. 2016年7月4日(月) 2:48 Jared Grubb via cfe-dev : > > El jun. 30, 2016, a las 19:31, Matthias Braun via cfe-dev < > cfe-...@lists.llvm.org> escribió: > > > On Jun 30, 2016, at 4:14 PM, Renato Golin via llvm-dev < > llvm-...@lists.llvm.org> wrote: > > > On 30 Ju

Re: [lldb-dev] [llvm-dev] Git Move: GitHub+modules proposal

2016-06-27 Thread NAKAMURA Takumi via lldb-dev
It has also submodules. https://github.com/llvm-project/llvm-project-submodule Both llvm-project(-tree) and (-submodule) have refs/notes/commits. On Tue, Jun 28, 2016 at 1:13 AM Renato Golin via llvm-dev < llvm-...@lists.llvm.org> wrote: > On 27 June 2016 at 17:03, Rafael Espíndola > wrote: > >

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

2016-05-31 Thread NAKAMURA Takumi via lldb-dev
TL;DR :-) Git-submodules works fine for bisecting for read-only use. I have the repo to do that. https://github.com/llvm-project/llvm-project-submodule With a simple hooks/post-checkout, It should help effective bisecting. https://github.com/chapuni/llvm-project-scripts/blob/master/hooks/post-che

Re: [lldb-dev] [Attn: Bot Owners!] Raising CMake minimum version to 3.4.3

2016-05-25 Thread NAKAMURA Takumi via lldb-dev
I am ready, regarding to, http://bb.pgr.jp/ On Wed, May 25, 2016 at 5:54 AM Chris Bieneman wrote: > Meant to send this yesterday, but I want to remind everyone that we’re > going to be raising the CMake minimum version to 3.4.3 next week. > > If you maintain bots please ensure that your bots are