search for: release_xx

Hello. I'm developing a LLVM based project and I'm using a fork of LLVM and Clang repos from https://github.com/llvm-mirror . The workflow was merging my work with release_XX branches from these repos, so now I have my commits interspersed with upstream ones. I'd be grateful for any advice on how should I move my work towards official git monorepo. I want to preserve my history, of course. Thanks in advance. -------------- next part -------------- An HTML attachme...

...velopment happens on the trunk, and then branches are created for each release. Changes are selectively folded into the release branch until the release is blessed, and then (generally speaking) the release branch isn't touched again. SAFECode works differently. With SAFECode, there is a release_xx branch for each release of LLVM that we support. For example, the SAFECode release_30 branch works with the release_30 branch of LLVM. The idea is to make it easy for people to grab updates to SAFECode that work with a particular LLVM version. The real difference is that SAFECode usually sti...

I always though the /tags/RELEASE_xx/final branch would hold the final, released tarball contents, but this does not appear to be the case, at least not for 3.1. I can confirm that diffing /tags/RELEASE_31/final and the 3.1 tarball shows some non-trivial changes. The 3.2 release seems to be okay though; the diff only shows changes i...

Won't it be http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_31/final/ On Tue, Jan 8, 2013 at 7:46 PM, Pankaj Gode <godepankaj at yahoo.com> wrote: > Hi All, > > I was checking for GIT or SVN versions corresponding to llvm3.1 release by > checking svn and git logs, but failed to find the exact match. > > I checked with r156747, which is the last version it shows

Hi, I'm learning the tutorial. http://llvm.org/docs/tutorial/ I'm wondering if there is already a git repository of the examples in the tutorial so that I don't have to copy the code from the webpage. Thanks! -- Regards, Peng

On Nov 13, 2012, at 7:52 AM, John Criswell <criswell at illinois.edu> wrote: >> John, it was not my intention to disrupt your work in any way. >> However, branching for release is a bit of a grey area and I >> have made a judgment call to branch SAFECode in sync with llvm. >> This could have been a bit overzealous but I am used to >> "release at any

Hi All, I was checking for GIT or SVN versions corresponding to llvm3.1 release by checking svn and git logs, but failed to find the exact match. I checked with r156747, which is the last version it shows in      http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_31/ but when I 'diff' this with the 'downloaded llvm3.1 release'(http://llvm.org/releases/download.html#3.1), then I

On 11/12/12 5:22 PM, 32bitmicro wrote: > John, > >> Dear Pawel and All, >> >> Pawel (and other release managers), can you ask the project maintainers >> for each project whether they want a release branch before creating it >> next time? Alternatively, can you leave branch creation up to the >> project maintainers as in the past? > I think asking