similar to: [LLVMdev] 2.0 Branch Creation - NOW

Branch has been created. CVS is open again. -Tanya On Mon, 6 Nov 2006, Tanya M. Lattner wrote: > > Please refrain from comitting to cvs. I will send email once I have finished > creating the branch. > > Thanks, > Tanya > >

Please refrain from comitting to cvs. I will send email once I have finished creating the branch. Thanks, Tanya

LLVMers, I will be creating the branch in 30 minutes (9PM PDT). At that time, I will send out mail announcing SVN commit access is suspended. Those with commit privileges should refrain from committing until I send out mail saying commit access is restored. Thanks, Tanya Lattner

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

LLVMers, I am creating the LLVM 2.2 branch now. Please refrain from committing to SVN until I send mail announcing the branch has been created. Thanks, Tanya

This is just a reminder that I will be creating the 1.8 release branch in 1 hour. Please refrain from checking into cvs after 9PM PDT until I send out email confirming the branch has been created. Thanks, Tanya Lattner

Branches have been created. You are free to checkin to cvs head again. I'll send mail once I have the prerelease tar balls up. Please continue to review and revise the documentation. I can fold this into the release later. Thanks, Tanya On Thu, 13 Apr 2006, Tanya Lattner wrote: > > I will be creating the release branch at 1:00pm PDT. Please refrain from > checking in from

I will be creating the release branch at 1:00pm PDT. Please refrain from checking in from 1:00-1:30pm. I will send email once I am done. Thanks, Tanya

LLVM Developers, It is now 1 week before I will create the 2.0 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before

The various intrinsic assert/crashes should all be fixed on mainline CVS (they are PR733, which I just fixed). The only ones that I'm wary of are: XPASS: /proj/llvm/build/../llvm/test/Regression/CFrontend/2004-02-20- StaticRedeclare.c.tr FAIL: /proj/llvm/build/../llvm/test/Regression/CFrontend/2005-12-04- DeclarationLineNumbers.c: In the former case, I would guess that the test isn't

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

Tanya M. Lattner wrote: > I'm asking that all platform maintainers and available llvm developers > review the nightly tester results. Please XFAIL any dejagnu tests that are > currently failing, fix any warnings, and review the results of the full > llvm test suite. If a test failure is determined to be something that > needs to be fixed before the release, please fix it or

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. Thanks, Tanya

> Hi Tanya, > > I do not really understand this strict rule :-) > While I get it from a CVS perspective, in Subversion > this is simply overkill. For making a branch you simply > select a revision X, do a "svn -rX up", test, > if successful, you do "svn info ." and use the URL > to make a repo -> repo copy: > > svn cp -rX URL BRANCHURL > >

> 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

I just updated again (both llvm and llvm-gcc). The only thing that changed was: P test/Regression/CFrontend/2005-12-04-DeclarationLineNumbers.c The regression test below was done *with* your llvm-gcc changes to llvm- expand.c. I don't know what the failures are all about, but I will try it again. If its the same, I'll let you know. Reid. On Thu, 2006-04-13 at 16:20 -0500, Chris Lattner

John Criswell wrote: > Dear All, > > Some of you may have noticed that our SSL certificate expired about half > an hour ago. We have a new SSL certificate, but we haven't had time to > install it. > > I am going to attempt to install the new certificate. This will > necessitate one server restart if I am successful and probably two if > I'm not. > >

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

LLVMers, It is now 1 week before I will create the 1.9 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before the

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.