similar to: [LLVMdev] svn issues

Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] svn issues"

2007 Jul 25
0
[LLVMdev] svn issues
Hi David, On Wed, 2007-07-25 at 10:38 -0500, David A. Greene wrote: > I'm getting a lot of errors from svn like this: > > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' > svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read response > body: Secure connection truncated (https://llvm.org) What is
2007 Jul 25
3
[LLVMdev] svn issues
On Wednesday 25 July 2007 11:06, Reid Spencer wrote: > Hi David, > > On Wed, 2007-07-25 at 10:38 -0500, David A. Greene wrote: > > I'm getting a lot of errors from svn like this: > > > > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' > > svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read > > response
2006 Aug 16
1
Re: 400 Bad Request error from svn
It's nice to see that the OS where CentOS gets its sources from also experiments the same error! I have been very busy lately so I haven't had the time to deal with the problem, probably later this week or early next week. As soon as I find something Ill let you know. Hopefully you'll do the same if you come across the solution first. PS. Forwarding this message to the mailing
2007 Jul 25
0
[LLVMdev] svn issues
On Wednesday 25 July 2007 11:45, David Greene wrote: > On Wednesday 25 July 2007 11:06, Reid Spencer wrote: > > Hi David, > > > > On Wed, 2007-07-25 at 10:38 -0500, David A. Greene wrote: > > > I'm getting a lot of errors from svn like this: > > > > > > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' > > > svn:
2009 Aug 10
3
[LLVMdev] svn down?
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? -Dave
2009 Aug 10
0
[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
2006 Aug 11
2
Subversion: 400 Bad request error
Here is my problem, On my network there is a subversion server to which everybody connects to and checks in/out code and documents. The workstations on the network are all based on Fedora core 3. And everybody's home directory is on a nfs share. This nfs share is mounted via the fstab. So no matter to which box a user logs in, his/her home dir is gonna be the same. Again, /home is a nfs
2010 Mar 30
3
[LLVMdev] Need help fixing 2.7 release blockers
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?)
2009 Aug 11
1
[LLVMdev] svn down?
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
2011 Apr 22
3
[LLVMdev] svn server permissions for top-level svn update
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
2007 Jul 25
0
[LLVMdev] [Fwd: Re: svn issues]
This just in from Oscar .. Reid -------- Forwarded Message -------- > From: Oscar Fuentes <ofv at wanadoo.es> > To: Reid Spencer <rspencer at reidspencer.com> > Subject: Re: svn issues > Date: Wed, 25 Jul 2007 19:09:17 +0200 > > Reid Spencer <rspencer at reidspencer.com> writes: > > > Hi David, > > > > On Wed, 2007-07-25 at 10:38 -0500,
2007 Jul 25
1
[LLVMdev] svn issues
David, Did upgrading to a newer version help at all? If so, I'd like to notify people to stay away from 1.3.1. What's the status? Reid. On Wed, 2007-07-25 at 12:07 -0500, David Greene wrote: > On Wednesday 25 July 2007 11:45, David Greene wrote: > > On Wednesday 25 July 2007 11:06, Reid Spencer wrote: > > > Hi David, > > > > > > On Wed, 2007-07-25 at
2008 Jul 10
4
Distributed Setup Suggestions
My company is approx 200 users. We have 10 offices each with 5-30 users each. A few offices work independently, but there has been a lot more inter-office work lately. I am looking for a way to provide fast local access to files stored in the same office as the user, but also acceptable performance for inter-office file transfers. We are currently using Oracle Drive for a central file server, it
2010 Apr 01
7
Press release: Virtual Communication Clouds :: New feature in Asterisk 1.8
FOR IMMEDIATE RELEASE Puerto Escondido, Mexico, April 1st, 2010: Digium launches Asterisk VCC (TM) - a new virtual communication platform for enterprises, the public sector and the home. =========================================================== Asterisk 1.8 will contain a stunning new technology for all Asterisk users world- wide - virtual communication clouds or VCC (TM). With this
2017 Jun 25
2
IMPORTANT: LLVM.org server move complete (SVN impact please read)
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: > >
2018 Feb 13
1
can't extract diffs from llvm svn any more
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
2012 Nov 17
0
[LLVMdev] Poll: Do you prefer Git or SVN for LLVM development?
Greg Fitzgerald <garious at gmail.com> writes: > I'm curious to know if the LLVM community is deeply split when it > comes to version control. If you have a second, could you please > vote? > > http://poll.pollcode.com/i597kq The result of this poll has little value in practice. In the past the project leader stated that the opinions of the most active contributors
2007 Jul 12
2
[LLVMdev] Installing clang
Really happy to hear llvm has the brand-new front-end. But, unfortunately, I failed to install it. When I 'svn co http://llvm.org/svn/llvm-project/cfe/trunk clang' in llvm/tools folder, I got this message.. svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 400 Bad Request (http://llvm.org) Am I missing
2010 Oct 06
1
[LLVMdev] RELEASE_28 SVN tag
Hello all, According to: http://llvm.org/releases/2.8/docs/GettingStarted.html#checkout folks can check out a specific release from Subversion. As of right now, RELEASE_28 contains folders for each of the release candidates, as opposed to the final content. Same goes for Clang. -Matt -------------- next part -------------- An HTML attachment was scrubbed... URL:
2011 Jul 08
0
[LLVMdev] type-system-rewrite branch near landing
>>  ~/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