search for: r273407

...om (as release-manager) answer why there were no >> commit-ids (release_381 SVN branch) sent to llvm-commits ML? > Sure, I already written this above - there is *no* such branch > (http://llvm.org/svn/llvm-project/llvm/branches/) > Hmm, I saw this on llvm-commits ML... [test-suite] r273407 - Creating release candidate final from release_381 branch http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160620/366816.html - Sedat - [1] http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160620/366815.html [2] http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-2016062...

...re were no > >> commit-ids (release_381 SVN branch) sent to llvm-commits ML? > > Sure, I already written this above - there is *no* such branch > > (http://llvm.org/svn/llvm-project/llvm/branches/) > > > > Hmm, I saw this on llvm-commits ML... > > [test-suite] r273407 - Creating release candidate final from release_381 > branch http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon- > 20160620/366816.html > > - Sedat - > > [1] http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon- > 20160620/366815.html > [2] http://lists.llvm.org/pi...

...the LLVM/Clang mirrors on GitHub. Unfortunately, I am missing a "release_381" branch at all on the GitHub repositories. I looked through the llvm-commits [1] and I only see two emails with the subject... "Creating release candidate final from release_381 branch" [test-suite] r273407 - Creating release candidate final from release_381 branch Tom Stellard via llvm-commits [lld] r273414 - Creating release candidate final from release_381 branch Tom Stellard via llvm-commits So, how should I know which is the corresponding SVN-commit-id for tagging myself in my local [llvm |...

>>> What you're probably missing is that 3.8.1 is made in release_38 >>> branch. So, everything is there and already mirrored. >>> >>> Source tarballs will be available upon the release. >> Which are just coming, now that final has been tested successfully. :) >> They'll be announced in the list and available here: >>

...nch) sent to llvm-commits ML? >>> > Sure, I already written this above - there is *no* such branch >>> > (http://llvm.org/svn/llvm-project/llvm/branches/) >>> > >>> >>> Hmm, I saw this on llvm-commits ML... >>> >>> [test-suite] r273407 - Creating release candidate final from release_381 >>> branch http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon- >>> 20160620/366816.html >>> >>> - Sedat - >>> >>> [1] http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon- >>&gt...

...fortunately, I am missing a "release_381" branch at all on the > GitHub repositories. > > I looked through the llvm-commits [1] and I only see two emails with > the subject... > > "Creating release candidate final from release_381 branch" > > [test-suite] r273407 - Creating release candidate final from > release_381 branch Tom Stellard via llvm-commits > [lld] r273414 - Creating release candidate final from release_381 > branch Tom Stellard via llvm-commits > > So, how should I know which is the corresponding SVN-commit-id for > taggin...

...mit-ids (release_381 SVN branch) sent to llvm-commits ML? >> > Sure, I already written this above - there is *no* such branch >> > (http://llvm.org/svn/llvm-project/llvm/branches/) >> > >> >> Hmm, I saw this on llvm-commits ML... >> >> [test-suite] r273407 - Creating release candidate final from release_381 >> branch http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon- >> 20160620/366816.html >> >> - Sedat - >> >> [1] http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon- >> 20160620/366815.html >&...

On Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ CCed all people who were involved in this thread ] > > Hi Tom, > > personally, I am interested to test the prebuilt-toolchains for > Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64. > The available toolchains are incomplete and thus useless. > > Just as a fact: There is still no