[LLVMdev] SAFECode and Poolalloc Branches for LLVM 2.6

[John Criswell]

Dear Erich,

We usually leave the creation of branches to developers who work on the 
project.  Branches can be created without any special administrative 
access (you just need commit access to the project in question).  If 
you're a Klee developer and need help creating a release_26 branch, 
please let me know; I can provide assistance.

Regards,

-- John T.


llvmdev at erichocean.oib.com wrote:
> Please create a similar branch for Klee; I've been working on porting 
> that to 2.7 as well.
>
> Best, Erich Ocean
>
> On Fri, Mar 5, 2010 at 8:43 PM, John Criswell (criswell at uiuc.edu) wrote:
> >
> > Dear SAFECoders and LLVMers,
> >
> > There is some new work on moving DSA to the new LLVM 2.7 API. I am
> > hoping to do something similar for SAFECode once the code freeze occurs.
> >
> > To keep things running smoothly, there are now release_26 branches for
> > the poolalloc and safecode projects. If you are using SAFECode,
> > Poolalloc, or DSA with LLVM 2.6, you will want to switch to these 
> branches.
> >
> > To get poolalloc and safecode out of these branches, use the following
> > SVN commands:
> >
> > svn co http://llvm.org/svn/llvm-project/poolalloc/branches/release_26
> > poolalloc
> > svn co http://llvm.org/svn/llvm-project/safecode/branches/release_26
> > safecode
> >
> > If you have any questions or problems compiling poolalloc or SAFECode,
> > please email llvmdev or svadev, respectively.
> >
> > -- John T.
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu> 
> http://llvm.cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> >
> >
> >