similar to: [LLVMdev] SVN/Git Mirror Hooks

How does the LLVM server keep the git svn mirror up to date? Are there hooks in the svn server that automatically update the git mirror? If so, are any of these tools public? I ask because I'm looking at setting up some mirrors at work and I may (I stress _may_) have a way to make git mirrors interact somewhat sanely with each other. But I need something that keeps a git mirror in sync

Hi David, > How does the LLVM server keep the git svn mirror up to date?  Are there > hooks in the svn server that automatically update the git mirror? Yes >  If so, are any of these tools public? It's just "git svn fetch" -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi, Has there been discussion about having svn mirror git instead of vice versa? I've been happy with the git+cmake+ninja combo for a while now, but the online docs suggests this configuration is second-class to svn+autotools+make. Is the community transitioning to any particular configuration? Thanks, Greg On Wed, Nov 14, 2012 at 9:19 AM, Anton Korobeynikov <anton at

This has been discussed many times. Might want to take a look in the mailing list archives. :) cmake and autotools are on roughly equal footing at this point with chandler and I handling each of them respectively and fairly quickly. git vs. svn is a different story though. -eric On Thu, Nov 15, 2012 at 8:31 AM, Greg Fitzgerald <garious at gmail.com> wrote: > Hi, > > Has there

> cmake and autotools are on roughly equal footing at this point with chandler > and I handling each of them respectively and fairly quickly. git vs. svn is > a different story though. Would you be willing to put this commitment to autotools in CODE_OWNERS.TXT? Sometimes I have needed to make changes to Makefiles and didn't know who was the right person to CC for it, so having an

Hello Everyone As you might already know, git mirrors of llvm repository started from repo.or.cz mirrors, where stuff was pushed almost by hands out of git-svn local copy. Right now we have official and automatically updated GIT mirrors on llvm.org and thus repo.or.cz mirrors look a bit redundant. However, they might still be useful, but definitely not within the current "push mode". It

Yeah, it seems that the time the mirror was created there were no release branches and therefore nothing was exported :) On Fri, Nov 20, 2015 at 8:13 PM, Hans Wennborg <hans at chromium.org> wrote: > On Thu, Nov 19, 2015 at 2:38 PM, Martell Malone via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi All, >> >> I am currently trying to test out a few things

Thanks, Anton. I always forget about llvm-admin :). I'd say converting all branches would be best, would help track the MCJIT work for example. Gaël, does that sound good to you? You're the one making all the commits these days :). ~Will On Sun, Jan 5, 2014 at 9:03 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello > > I can create a mirror, this is not

Hi all, Don't suppose VMKit could be added to the set of subprojects with official git mirrors? Please and thank you! :) ~Will

Chen, Teemu is asking "the official git mirror" and he oughta know where the svn repo is. ;) Teemu, I have created an unofficial one; https://github.com/chapuni/dragonegg Excuse me, I might not update it so frequently. Anton, please provide us the official dragonegg.git! ...Takumi

14 KB/s now. Yesterday 40 KB/s. Is that transitory or there is no enough bandwidth on llvm.org?

> Anton, please provide us the official dragonegg.git! Done! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Do pushes to the LLVM git mirror get forwarded to the svn trunk automatically? For various reasons it may be more convenient for me to work on LLVM through git but I don't want to go through a lot of pain to send patches to trunk via git. It should be easy. Does anyone do their primary development via the git mirror? How well does it work? -Dave

Hi Oscar, > 14 KB/s now. Yesterday 40 KB/s. > Is that transitory or there is no enough bandwidth on llvm.org? Something is wrong on your side: $ git clone http://llvm.org/git/llvm.git Cloning into llvm... remote: Counting objects: 607409, done. remote: Compressing objects: 100% (118270/118270), done. Receiving objects: 2% (13924/607409), 3.87 MiB | 402 KiB/s -- With best regards, Anton

Hello Anton and Takumi. Anton Korobeynikov <anton at korobeynikov.info> writes: >> 14 KB/s now. Yesterday 40 KB/s. >> Is that transitory or there is no enough bandwidth on llvm.org? > Something is wrong on your side: > > $ git clone http://llvm.org/git/llvm.git > Cloning into llvm... > remote: Counting objects: 607409, done. > remote: Compressing objects: 100%

Hello, David > Do pushes to the LLVM git mirror get forwarded to the svn trunk > automatically? No, it's one-way due to many reasons. However you can use it to "bootstrap" git-svn metadata and do commits via the git-svn facilities. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

> for Aaron => git mirror stopped working. > I'm going to fix stuff asap. Should be working now. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Does anyone know if the llvm.org git mirror is down or just slow? The clang repo is missing about the last 2 hours of commits.

Hello, Nathan First of all, I would like to mention that COFF MC backend will be a really good contribution to LLVM! > I have created a minimally functional Win32 COFF Exporter using the new MC > framework. I made some minor changes to other libraries to allow me to plug > it in without building it as part of the LLVM project. I wanted to share it > but wasn't sure how to go

Hello Everyone I'm going to rebuild GIT mirrors to provide more consistent tags / branches. Basically, the contents will be the same, but naming scheme will change. So, trunk will go to svn/trunk, branches/* will got to svn/branches/* and tags/* will go to svn/tags/* This might break some scripts, etc. So, if anyone has some objections wrt this - please let me know. PS: First clang.git