similar to: [LLVMdev] llvm.org svn/web down tonight

This is just a reminder that I will be creating the 2.0 release branch tonight at 9pm PDT (GMT-7). I'll send out email before and after branch creation. CVS commit access will not be allowed during this time. Thanks, Tanya

LLVMers, I will be creating the 2.4 branch at 9pm PDT tonight. Please attempt to limit your commits to bug fixes and documentation changes. I'll send out email after the branch creation tonight. Thanks, Tanya

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

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 > _______________________________________________

> On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: >> Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. > > What does re-creating mean? Why can't the previously-created 2.5 branch > simply be updated? It means deleting the branch and creating a new one. > I ask because svn history will look a little wierd and it makes it harder for

Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. -Tanya

On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: > Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. What does re-creating mean? Why can't the previously-created 2.5 branch simply be updated? I ask because svn history will look a little wierd and it makes it harder for third parties to track revisions and do merges.

(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

LLVMers, Tonight is the 2.2 code freeze. I will be creating the branch at 9PM PST. Commit access to SVN will be closed for approximately one hour (or less). I'll send one email before I start the release branch creation and an email when I am finished. If you have any questions, please let me know. Thanks, Tanya 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

I will be creating the branch at 9PM PST. Please refrain from checking in any large changes until after the branch creation. I'm still seeing unexpected dejagnu failures for PPC and X86. Platform maintainers, please XFAIL these and file bugzilla bugs. Email me if you have concerns or questions. -Tanya

The deadline is tonight! Get your proposal in :) -Tanya > On Jul 27, 2018, at 11:19 AM, Tanya Lattner <tanyalattner at llvm.org> wrote: > > Just a reminder that this deadline is coming up. Submit your proposal today! > > -Tanya > >> On Jun 29, 2018, at 10:59 AM, Tanya Lattner <tanyalattner at llvm.org <mailto:tanyalattner at llvm.org>> wrote: >>

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

Dear All, Just a reminder that llvm.org will be unavailable on Feb. 1 (tonight!) and Feb. 4 for backup and software upgrade. That includes SVN services and the web pages. The mailing lists will remain up. -- John T. On 1/28/13 4:28 PM, Tanya Lattner wrote: > To be clear: > Friday, February 1, 2013 & Monday, February 4, 2013 > > On Jan 28, 2013, at 2:08 PM, Tanya Lattner

On Sep 15, 2010, at 12:46 AM, Albert Graef wrote: > Bill Wendling wrote: >> Release testing of Release Candidate 1 is finished. I'll be tagging >> Release Candidate 2 tonight. If there are any fixes you want in, please >> get them approved as soon as possible. > > Are there any tarballs for the release candidates available? Tanya used > to make these available

Please try to limit today's checkins to critical bug fixes. The code freeze/branch creation will happen at 9PM PST. Thanks, Tanya

Bill Wendling wrote: > Release testing of Release Candidate 1 is finished. I'll be tagging > Release Candidate 2 tonight. If there are any fixes you want in, please > get them approved as soon as possible. Are there any tarballs for the release candidates available? Tanya used to make these available for previous releases, but I haven't been able to find any for testing 2.8.

On Wed, 15 Sep 2010 01:50:24 -0700 Bill Wendling <wendling at apple.com> wrote: > On Sep 15, 2010, at 12:46 AM, Albert Graef wrote: > > > Bill Wendling wrote: > >> Release testing of Release Candidate 1 is finished. I'll be tagging > >> Release Candidate 2 tonight. If there are any fixes you want in, > >> please get them approved as soon as

All, The following llvm.org certificates will be renewed tomorrow, Friday Sept 22nd at ~7:30AM PDT. bugs.llvm.org <http://bugs.llvm.org/> clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/> clang.llvm.org <http://clang.llvm.org/> compiler-rt.llvm.org <http://compiler-rt.llvm.org/> dragonegg.llvm.org <http://dragonegg.llvm.org/> git.llvm.org

Good day Tanya, I would just like to clarify this for myself and a few other people who maybe wondering, Does this code freeze apply to; * Clang. * Compiler-RT. Thanks for your time, Best Regards, Edward O'Callaghan. 2009/8/17 Tanya Lattner <lattner at apple.com>: > LLVMers, > > The 2.6 code freeze is this friday, August 21, at 9pm PDT. > > All major changes should