similar to: [LLVMdev] svn down?

On Aug 10, 2009, at 2:59 PM, David Greene wrote: > I've been getting this on svn update all day: > > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' > svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 403 Forbidden > (http://llvm.org) > > Is this related to the server problems that have been going on for a > while? > svn is

On Monday 10 August 2009 17:42, Tanya Lattner wrote: > On Aug 10, 2009, at 2:59 PM, David Greene wrote: > > I've been getting this on svn update all day: > > > > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' > > svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 403 Forbidden > > (http://llvm.org) > > > > Is

Hello, I had a question tangentially related to svn. I am very new to LLVM. It seems like a long road to making my own backend, but I am wading through the documentation and experimenting with the code and having a lot of fun with it. I would like to try various experimental things out and also keep track of the latest changes. It seems like this is very difficult to do with svn.

Hi, My svn working copy mirrors the layout of the whole svn repository, from llvm-project downwards, so I have: ~/svn/llvm-project/ ~/svn/llvm-project/llvm/ ~/svn/llvm-project/llvm/trunk/ # lots of stuff in here ~/svn/llvm-project/cfe/ ~/svn/llvm-project/cfe/trunk/ # and lots of stuff in here (and likewise for test-suite, llvm-gcc-4.2 and dragonegg) This is nice because I can do "svn

On Tuesday 30 March 2010 17:45:16 David Greene wrote: > On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > > Please take a look at all release blockers: > > http://llvm.org/bugs/show_bug.cgi?id=6586 > > 5893 is not release-critical according to Doug. > > 6640 appears to be a test system problem with a patch available (one of the > ones you're working on?)

>>  ~/svn/llvm-project/llvm/branches$ svn up >>  svn: Server sent unexpected return value (403 Forbidden) in response >> to REPORT request for '/svn/llvm-project/!svn/vcc/default' > > I think that explicitly returns Forbidden just to avoid the strain on > the server; if you have any write access, you should have write access > to everything. Off topic, but

On Mon, May 12, 2014 at 9:34 AM, Manuel Klimek <klimek at google.com> wrote: > It seems that we cannot execute svn commands against llvm-project any more: > $ svn diff -r 208457:208458 'http://llvm.org/svn/llvm-project' > svn: access to '/svn/llvm-project/!svn/vcc/default' forbidden > > Tanja, any idea what changed? > (Tanya, sorry for messing up the name,

On Mon, May 19, 2014 at 1:48 PM, Alex Bradbury <asb at asbradbury.org> wrote: > On 12 May 2014 08:35, Manuel Klimek <klimek at google.com> wrote: > > On Mon, May 12, 2014 at 9:34 AM, Manuel Klimek <klimek at google.com> > wrote: > >> > >> It seems that we cannot execute svn commands against llvm-project any > >> more: > >> $ svn

On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > Please take a look at all release blockers: > http://llvm.org/bugs/show_bug.cgi?id=6586 5893 is not release-critical according to Doug. 6640 appears to be a test system problem with a patch available (one of the ones you're working on?) Which bugs do you have patches for? I don't want to start looking at something if

On Thu, Jul 7, 2011 at 12:55 AM, Jay Foad <jay.foad at gmail.com> wrote: >> 1. Clang - Jay, do you have a patch for this? > > Yes. It's good enough to build most of LLVM+Clang, except for a couple > of files. But I'm running out of time and expertise to be able to fix > the remaining bits. Some specific concerns: > > 1. Many Objective-C(++) tests fail, because

All, There has been a huge lack of response to the release. We need people to help fix regressions and to participate in testing the release. Without this support, I see no reason that the release team should spend their time qualifying a release. We need to get all regressions fixed before 2.7 can continue onto pre-release2. Please take a look at all release blockers:

Adding +Eric Liu <ioeric at google.com> who helps with Phabricator.... On Sun, Jun 25, 2017 at 3:15 PM Davide Italiano via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Sun, Jun 25, 2017 at 12:32 PM, Anton Korobeynikov > <anton at korobeynikov.info> wrote: > > Thanks, fixed. > > > > Also, FWIW, phabricator commit mails are broken. Example: > >

> 1. Clang - Jay, do you have a patch for this? Yes. It's good enough to build most of LLVM+Clang, except for a couple of files. But I'm running out of time and expertise to be able to fix the remaining bits. Some specific concerns: 1. Many Objective-C(++) tests fail, because they use implicitly defined structs for various ObjC runtime data structures; the ASTConsumer

Hi, As a Linux package maintainer I tend to follow LLVM mostly towards the end of each release cycle; nevertheless, I sometimes need to keep track of multiple LLVM branches at the same time. It would be great if I could use Git's SVN to clone the repository once, and then have the full version history available locally in a compact format. As a bonus, this will reduce the load on the server

On Mon, Aug 10, 2009 at 6:18 PM, Ray Fix<rayfix.ml at gmail.com> wrote: > > Hello, > I had a question tangentially related to svn.    I am very new to LLVM.  It > seems like a long road to making my own backend, but I am wading through the > documentation and experimenting with the code and having a lot of fun with > it.  I would like to try various experimental things out

It used to be that you could extract the diff for change with a command like: svn diff -c 323998 http://llvm.org/svn/llvm-project/cfe/trunk I now get: svn: E175013: Access to '/svn/llvm-project/!svn/vcc/default' forbidden I uses this to extract upstream patches for release version of llvm products to add to the packages in FreeBSD. If there's another prefered option please let me

On Mar 30, 2010, at 4:04 PM, David Greene wrote: > On Tuesday 30 March 2010 17:45:16 David Greene wrote: >> On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: >>> Please take a look at all release blockers: >>> http://llvm.org/bugs/show_bug.cgi?id=6586 >> >> 5893 is not release-critical according to Doug. >> >> 6640 appears to be a test

Thanks, fixed. On Sun, Jun 25, 2017 at 10:28 PM, Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Sat, Jun 24, 2017 at 4:02 PM, Tanya Lattner via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> LLVMers, >> >> We have completed the move to the new server for LLVM.org. One casualty of >> this move was that svn.llvm.org was NOT enabled

On Sat, Mar 27, 2010 at 4:38 PM, Michel Alexandre Salim <michael.silvanus at gmail.com> wrote: >> git svn clone --no-minimize-url -s http://llvm.org/svn/llvm-project/llvm llvm > Initialized empty Git repository in /home/inf2/i2staff/salim/checkout/llvm/.git/ > RA layer request failed: Server sent unexpected return value (403 > Forbidden) in response to REPORT request for >

> If llvm-admin is meant to be mailed in some circumstances, perhaps the > listinfo page should say something other than "DO NOT MAIL THIS > LIST!"? Yes, I saw that too. I presumed that it was okay to mail this list because I saw a suggestion in an older post[1] to send messages to it. But perhaps I'm wrong. [1]