similar to: [LLVMdev] New 'www' svn module

The svn server is back online (as is the web server). However, there are a few issues remaining: - Doxygen is not updating. - Auto-update of websites not working due to permissions issues. I'll update once these 2 things are working again, but I hope to keep the web/svn server up from now on. If you have problems with committing, please let me know. This should work for people committing

Hy, Tanya > Some comments: > - Please follow the developers policy for making patches: > http://llvm.org/docs/DeveloperPolicy.html#patches > OK. My fault here. Will check some of your observations and resubmit. > - I think if we are going to upgrade, we should totally switch to 2.6 > instead of allowing both. This will make diffs easier to read when people > regenerate

Please always make patches against TOT: http://llvm.org/docs/DeveloperPolicy.html#patches -Tanya On Aug 17, 2011, at 8:29 AM, Villmow, Micah wrote: > Here is a patch for LLVM 2.9 that adds AMDIL as a valid target triple to LLVM. > I'll get an updated patch for LLVM TOT if this doesn't patch cleanly next. > > Micah >

> The current SVN repository has several modules at the top level (llvm, > test-suite, java, stacker, etc.). The modules contain the software that > makes up the LLVM Project. However, there is nothing at the top level > that explains any of this. So, I am considering doing the following at > the top level of the repository (i.e. in > http://llvm.org/svn/llvm-project): > >

> * I'm using Autoconf 2.61, and it is compatible with the syntax used > by LLVM, but AutoRegen.sh insists I need 2.5x. > > * There is a bug in the AutoRegen.sh that appears when you try to > regenerate configure scripts for your project outside the LLVM > source tree: an shell "read" command missing a parameter. > > The patch was tested on 2.2, but I think

The web server is back up! I apologize for the short notice. We appear to have fixed the problem (thanks Anton!). In the future, we will try to provide at least 30 minutes notice (min, but usually more) when shutting down the server. This was a special case because of some subversion tasks did not get taken care of. Thanks for understanding, -Tanya On Fri, 29 Jun 2007, Tanya M. Lattner

Going down now. I'll send mail when its back up. -Tanya On Oct 26, 2011, at 3:12 PM, Tanya Lattner wrote: > Just FYI, I will be upgrading to 1.7.1 (from 1.5.4). > > Thanks, > Tanya > > On Oct 26, 2011, at 3:05 PM, Tanya Lattner wrote: > >> I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. >> >> You will

Hi Tanya, On Sun, 2007-07-01 at 19:38 -0700, Tanya M. Lattner wrote: > > The current SVN repository has several modules at the top level (llvm, > > test-suite, java, stacker, etc.). The modules contain the software that > > makes up the LLVM Project. However, there is nothing at the top level > > that explains any of this. So, I am considering doing the following at >

Just FYI, I will be upgrading to 1.7.1 (from 1.5.4). Thanks, Tanya On Oct 26, 2011, at 3:05 PM, Tanya Lattner wrote: > I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. > > You will notice that all web and of course svn services will be down during this time. > > Thanks, > Tanya > _______________________________________________

The document: http://llvm.org/docs/DeveloperPolicy.html refers to using utils/mkpatch. However when using mkpatch it complains about directories no longer under version control. Specifically directories lib/Debugger and win32 in mkpatch's source line: svn diff -x -u >> "$NAME".patch.raw 2>&1 \ autoconf docs utils include lib/System lib/Support lib/VMCore

On May 9, 5:37 pm, "Tanya M. Lattner" <to... at nondot.org> wrote: > LLVMers, > > I will be creating the 2.3 release branch today at 9PM PDT. During that > time, commit access to SVN will be forbidden. I will send out mail shortly > before the branch creation, and once it has been completed. Hi Tanya, I do not really understand this strict rule :-) While I get it

I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. You will notice that all web and of course svn services will be down during this time. Thanks, Tanya

The transition to the new server is complete. If you find something is broken or not working correctly, please send mail to the list (llvmdev or cfe-dev). The demo page and docs should be fully functional. Thank you for your patience during this time. Thanks, Tanya

@Tobias The poly docs build step is still failing, but due to a bug in the particular version of Sphinx used by the www-scripts builder. This seems like something best worked around inside poly. The builds take place hourly and their output is reported on the www-scripts at lists.llvm.org mailing list. On Thu, May 25, 2017 at 12:58 AM, Tobias Grosser <tobias.grosser at inf.ethz.ch > wrote:

>> Considering that everyone is managing just fine with cvs, anything >> discussed about the differences between cvs and *X* is not a show stopper. > > I would have used the term "coping just fine" with cvs. Yeah, it works. > But, is it productive? efficient? easy? fast? .. none of those. There > are better alternatives and that's why we're discussing it.

(I apologize if you get multiples of this mail, we are having mailing list issues) FYI..tonight from 10:00PM-12:00AM PDT the web server and subversion access will be down. I suspect that we won't need that entire 2 hour time block, but just plan on not having httpd access during that time. Thanks, Tanya

Hi, Got the same error, switching to https fixes the issue. Regards, ismail On Wed, Jun 28, 2017 at 12:50 AM, Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I haven’t gotten a lot of people mentioning this specific error, so I hope > others will speak up. > > What version of the svn client are you using? > > Thanks, > Tanya > > On Jun 27, 2017,

All, The current SVN repository has several modules at the top level (llvm, test-suite, java, stacker, etc.). The modules contain the software that makes up the LLVM Project. However, there is nothing at the top level that explains any of this. So, I am considering doing the following at the top level of the repository (i.e. in http://llvm.org/svn/llvm-project): 1. /README.html Just a short

Hi all, Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source tarballs here: http://llvm.org/pre-releases/3.0/ A Word About Patches I neglected to send out instructions on how to get patches into the LLVM 3.0 branch. All patches must

I've included a patch which does not remove mkpatch but does remove diff search directories which caused a failure because those directories were no longer in svn. I was uncomfortable removing mkpatch since I believe it helps document creating patches for beginners who do not use separate source and build (object) root directories. Its existence is also expected by readers of: