similar to: Add more projects into Git monorepo

Is this intended to be the monorepo that eventually becomes the official repo, because if so I strongly object to putting libunwind, libc++ and libc++abi in it. I have recently been working on bring-up for libc++ and libunwind on a new platform and the integration of libunwind with the LLVM build system is already annoying (you can’t build it unless you have a working C++ standard library

On Sun, May 7, 2017 at 12:07 AM, NAKAMURA Takumi via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I have done just now. 5 repos added including debuginfo-tests. > ATM, it includes 17 repos total. > > - Created the new repo; https://github.com/llvm- > project/llvm-project-20170507.git > Branches will come later. > - The previous repository has a merge commit that

Possibly unrelated but since someone asked, I wonder why we don’t have monorepo for releases? For example a .tar.s containing all LLVM6.0 components placed at correct location Zhang > 在 2018年8月30日，18:16，Dean Michael Berris via llvm-dev <llvm-dev at lists.llvm.org> 写道： > > Thanks! >> On Thu, Aug 30, 2018 at 7:31 PM NAKAMURA Takumi <geek4civic at gmail.com> wrote:

The monorepo prototype at https://github.com/llvm-project/llvm-project-20170507 is currently 9 hours behind. I forget who’s responsible for the script(s) updating the monorepo(s), and it would be great if we can inform them of the state of the monorepo. Cheers -- Dean

On Fri, Nov 16, 2018 at 4:04 PM NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Hello, David. > > On Sat, Nov 17, 2018 at 7:46 AM David Jones via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi James, >> >> I've started working with the prototype layout in context of Google's >> internal infrastructure. With deep apologies, I

Anton has fixed it. 2018年8月30日(木) 17:23 Martin Storsjö via llvm-dev <llvm-dev at lists.llvm.org>: > On Thu, 30 Aug 2018, Dean Michael Berris via llvm-dev wrote: > > > The monorepo updates seem to have been stuck for an hour now. > > > > Is this expected? > > It seems like the regular per-project git repos also are stuck right now - > which probably

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-dev at lists.llvm.org> wrote: > On 27 June 2016 at 17:03, Rafael Espíndola <rafael.espindola at gmail.com> > wrote: > > I think that trying to create a

Hi all, the monorepo contains a Go frontend called 'llgo' (in the llgo/ top level folder). It apparently hasn't been active since 2017 and before that it wasn't very active either (there were 13 commits in 2016 apparently, most of it minor fixes). I would propose that we remove it from the monorepo for the following reasons: * It is apparently unmaintained. * It only supports a

On 9 May 2017, at 16:59, Mehdi AMINI <joker.eph at gmail.com> wrote: > > I'm not sure if you really read the last sentence of what I wrote, or if you followed the previous discussions on the plan here? > At this point I believe that this concern is non-existent per the read-only individual repo. The read-only repo is only useful if you don’t intend to contribute stuff back

Yep - delete it. If someone wants it back they can resurrect it from version control & explain why it's worth adding back in. On Mon, Feb 10, 2020 at 9:17 AM Jonas Devlieghere via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Thanks for bringing this up! Strong +1 from me for all the reasons > you've mentioned. > > On Mon, Feb 10, 2020 at 8:42 AM Raphael Isemann

On 8 May 2017, at 20:51, Mehdi AMINI <joker.eph at gmail.com> wrote: > > > 2017-05-07 1:01 GMT-07:00 David Chisnall via llvm-dev <llvm-dev at lists.llvm.org>: > Is this intended to be the monorepo that eventually becomes the official repo, because if so I strongly object to putting libunwind, libc++ and libc++abi in it. I have recently been working on bring-up for libc++

Done thusly: echristo at athyra ~/r/llvm-project> git push To github.com:llvm/llvm-project.git 936d1427da1..372bfc65deb master -> master On Mon, Feb 10, 2020 at 10:02 AM Eric Christopher <echristo at gmail.com> wrote: > OK. I'll get it. > > -eric > > On Mon, Feb 10, 2020 at 9:58 AM Peter Collingbourne <peter at pcc.me.uk> > wrote: > >> Sure,

Sure, that's fine with me. Peter On Mon, Feb 10, 2020 at 9:57 AM Eric Christopher via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Calling pcc real fast :) > > -eric > > On Mon, Feb 10, 2020 at 9:49 AM David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Yep - delete it. If someone wants it back they can resurrect it from >>

On 9 May 2017, at 15:58, Mehdi AMINI <joker.eph at gmail.com> wrote: > I'd expect any CI system to be able to cache this. > Also if you're issue is archiving a lot of build artifacts, the constant cost of the checkout isn't gonna matter that much. > Finally, the read-only individual repo can still be used by CI, which address this entirely. If we want to pull in new

Hi folks, I recently started getting errors when I fetch from the github monorepo ( https://github.com/llvm-project/llvm-project-20170507). They look like this: $ git fetch error: cannot lock ref 'refs/tags/release_600': there is a non-empty directory '.git/refs/tags/release_600' blocking reference 'refs/tags/release_600' >From

"The llgo frontend has been removed for now, but may be resurrected in the future." Thoughts? -eric On Tue, Aug 25, 2020 at 2:18 PM Hans Wennborg via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Can someone add a mention about the llgo removal to the release notes? > > Thanks, > Hans > > On Fri, Feb 14, 2020 at 3:40 PM James Y Knight via llvm-dev >

Nope, it wasn't all reverted -- the llgo implementation remains deleted. There's been some confusion borne out of unfortunate naming -- only the file "llvm/tools/llvm-go/llvm-go.go" was reinstated. Despite its confusing name, this tool is *not* a go implementation, and has effectively nothing to do with llgo. It's only a tiny utility script used by the llvm build process for

> On May 9, 2017, at 9:06 AM, Mehdi AMINI via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > 2017-05-09 9:03 GMT-07:00 David Chisnall <David.Chisnall at cl.cam.ac.uk <mailto:David.Chisnall at cl.cam.ac.uk>>: > On 9 May 2017, at 16:59, Mehdi AMINI <joker.eph at gmail.com <mailto:joker.eph at gmail.com>> wrote: > > > > I'm not

> On Jul 28, 2016, at 12:05 PM, Justin Lebar <jlebar at google.com> wrote: > >>> The decision of whether or not to include these projects >>> affects only read-write consumers of these projects -- of which there >>> are relatively few people. >> >> Maybe there are few, but the impact is non-insignificant. Also I think the opinions of the

On 27 June 2016 at 22:55, NAKAMURA Takumi via cfe-dev <cfe-dev at lists.llvm.org> wrote: > It has also submodules. > https://github.com/llvm-project/llvm-project-submodule > > Both llvm-project(-tree) and (-submodule) have refs/notes/commits. I really like this too, and think Takumi has basically solved 90% of the problem for us already. We may want to add an "rN" line