llvm dev - Feb 2016 - [3.8 Release] RC3 has been tagged

[ Original posting see [1] ]
>From [1]:
...
Added:
    llvm/tags/RELEASE_380/rc3/   (props changed)
      - copied from r261685, llvm/branches/release_38/
...

The LLVM Git repositories have no "rc3" tag in "release_38"
branch (as
an example llvm.git#release_38 see [2]).

Who is responsible for that or maybe better... can you activate the
responsible(s)?

Helpful is to add tags for both SVN and Git repositories synchronously.

Thanks!

Regards,
- Sedat -

[1] http://lists.llvm.org/pipermail/llvm-dev/2016-February/095756.html
[2] https://github.com/llvm-mirror/llvm/tree/release_38

On Wed, Feb 24, 2016 at 7:49 AM, Sedat Dilek <sedat.dilek at gmail.com>
wrote:
> [ Original posting see [1] ]
>
> From [1]:
> ...
> Added:
>     llvm/tags/RELEASE_380/rc3/   (props changed)
>       - copied from r261685, llvm/branches/release_38/
> ...
>
> The LLVM Git repositories have no "rc3" tag in
"release_38" branch (as
> an example llvm.git#release_38 see [2]).
>
> Who is responsible for that or maybe better... can you activate the
> responsible(s)?
>
> Helpful is to add tags for both SVN and Git repositories synchronously.
>
> Thanks!
>
> Regards,
> - Sedat -
>
> [1] http://lists.llvm.org/pipermail/llvm-dev/2016-February/095756.html
> [2] https://github.com/llvm-mirror/llvm/tree/release_38
I looked through some older emails and have CCed Anton.

I checked out from Git not knowing what rc3 is for llvm | clang |
compiler-rt, I will simply use realase_38 Git branch and then see.
Official (source) tarballs will take some time...

- Sedat -

On Wed, Feb 24, 2016 at 10:13 AM, Sedat Dilek <sedat.dilek at gmail.com>
wrote:
> On Wed, Feb 24, 2016 at 7:49 AM, Sedat Dilek <sedat.dilek at
gmail.com> wrote:
>> [ Original posting see [1] ]
>>
>> From [1]:
>> ...
>> Added:
>>     llvm/tags/RELEASE_380/rc3/   (props changed)
>>       - copied from r261685, llvm/branches/release_38/
>> ...
>>
>> The LLVM Git repositories have no "rc3" tag in
"release_38" branch (as
>> an example llvm.git#release_38 see [2]).
>>
>> Who is responsible for that or maybe better... can you activate the
>> responsible(s)?
>>
>> Helpful is to add tags for both SVN and Git repositories synchronously.
>>
>> Thanks!
>>
>> Regards,
>> - Sedat -
>>
>> [1] http://lists.llvm.org/pipermail/llvm-dev/2016-February/095756.html
>> [2] https://github.com/llvm-mirror/llvm/tree/release_38
>
> I looked through some older emails and have CCed Anton.
>
> I checked out from Git not knowing what rc3 is for llvm | clang |
> compiler-rt, I will simply use realase_38 Git branch and then see.
> Official (source) tarballs will take some time...
>
> - Sedat -
[ LLVM.git#release_38 ]

wearefam at fambox:~/src/llvm-toolchain/llvm-git$ LC_ALL=C git log -1
commit bb6f14e3581c78509405a3d415e72821db8a2066
Author: Quentin Colombet <qcolombet at apple.com>
Date:   Mon Feb 22 22:27:47 2016 +0000

    [AArch64] Fix bug in prolog clobbering live reg when shrink wrapping.

    This adapts r261349 to the release branch.


    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_38 at 261586
91177308-0d34-0410-b5e6-96231b3b80d8

[ CLANG.git#release_38 ]

wearefam at fambox:~/src/llvm-toolchain/clang-git$ LC_ALL=C git log -1
commit b98cd9d6a300bcd4863a26786bb1b5d782dcecc0
Author: Hans Wennborg <hans at hanshq.net>
Date:   Tue Feb 23 21:20:39 2016 +0000

    Merging r261669:
    ------------------------------------------------------------------------
    r261669 | aaronballman | 2016-02-23 10:55:15 -0800 (Tue, 23 Feb
2016) | 1 line

    Amends r252104 to evaluate the controlling expression in an
unevaluated context. This eliminates false-positive diagnostics about
null pointer dereferences (etc) in the controlling expression.
    ------------------------------------------------------------------------


    git-svn-id:
https://llvm.org/svn/llvm-project/cfe/branches/release_38 at 261684
91177308-0d34-0410-b5e6-96231b3b80d8

[ COMPILER-RT.git#release_38 ]

wearefam at fambox:~/src/llvm-toolchain/compiler-rt-git$ LC_ALL=C git log -1
commit 31769223eb782e7b03655810d00dfdec66467d51
Author: Hans Wennborg <hans at hanshq.net>
Date:   Fri Feb 19 19:43:25 2016 +0000

    Merging r261148:
    ------------------------------------------------------------------------
    r261148 | samsonov | 2016-02-17 12:40:10 -0800 (Wed, 17 Feb 2016) | 1 line

    [TSan] PR26609: Fix two test cases.
    ------------------------------------------------------------------------


    git-svn-id:
https://llvm.org/svn/llvm-project/compiler-rt/branches/release_38 at 261359
91177308-0d34-0410-b5e6-96231b3b80d8

I have tagged them as "rc3" in my local Git repositories.

[ EXAMPLE ]

$ cd llvm-git

$ git tag 3.8.0rc3 bb6f14e3581c

$ PKGNAME="llvm" ; VER="3.8.0rc3" ;
PREFIX="$PKGNAME-$VER" ;
TARBALL="$PREFIX.src.tar.xz"

$ git archive --format=tar --prefix=$PREFIX/ $VER | xz -2ec > ../$TARBALL

$ cd ..

$ sha256sum $TARBALL > $TARBALL.sha256sum


- Sedat -

Git tags and SVN tags are completely different beasts (git tag is
simply a "second name" attached to revision, while on svn the tag
could be arbitrary different). There is no way to automate the process
- in general svn tag might not correspond (by contents) to any other
revision in the repository.

The only way to somehow emulate svn tags on git is to create a
separate branch on each tag, however, this is very redundant provided
that we're already having a release branch.

On Wed, Feb 24, 2016 at 12:13 PM, Sedat Dilek <sedat.dilek at gmail.com>
wrote:
> On Wed, Feb 24, 2016 at 7:49 AM, Sedat Dilek <sedat.dilek at
gmail.com> wrote:
>> [ Original posting see [1] ]
>>
>> From [1]:
>> ...
>> Added:
>>     llvm/tags/RELEASE_380/rc3/   (props changed)
>>       - copied from r261685, llvm/branches/release_38/
>> ...
>>
>> The LLVM Git repositories have no "rc3" tag in
"release_38" branch (as
>> an example llvm.git#release_38 see [2]).
>>
>> Who is responsible for that or maybe better... can you activate the
>> responsible(s)?
>>
>> Helpful is to add tags for both SVN and Git repositories synchronously.
>>
>> Thanks!
>>
>> Regards,
>> - Sedat -
>>
>> [1] http://lists.llvm.org/pipermail/llvm-dev/2016-February/095756.html
>> [2] https://github.com/llvm-mirror/llvm/tree/release_38
>
> I looked through some older emails and have CCed Anton.
>
> I checked out from Git not knowing what rc3 is for llvm | clang |
> compiler-rt, I will simply use realase_38 Git branch and then see.
> Official (source) tarballs will take some time...
>
> - Sedat -


-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University