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

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

On Wed, Feb 24, 2016 at 2:07 PM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
> 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.
>
The release-announce to v3.8.0rc3 listed only one single SVN revision
- not sure this was for LLVM SVN.
The SVN revisions for clang (cfe) and compiler-rt were not announced.
For me this means to look at the SVN online repositories and check -
which is not very (Git-)user-friendly.

- Sedat -
> 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

On Wed, Feb 24, 2016 at 5:15 AM, Sedat Dilek <sedat.dilek at gmail.com>
wrote:
> On Wed, Feb 24, 2016 at 2:07 PM, Anton Korobeynikov
> <anton at korobeynikov.info> wrote:
>> 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.
>>
>
> The release-announce to v3.8.0rc3 listed only one single SVN revision
> - not sure this was for LLVM SVN.
> The SVN revisions for clang (cfe) and compiler-rt were not announced.
> For me this means to look at the SVN online repositories and check -
> which is not very (Git-)user-friendly.
SVN revisions are global to the repository (in SVN terms, llvm, cfe,
etc. are modules within the repository). To get the latest change in
the cfe and compiler-rt modules on the 3.8 branch, you'd need to look
for the last commit on the branch with revision <= the revision I
tagged at. It looks like you've found the right ones.

I agree this isn't very git user friendly, but as Anton pointed out it
seems tricky to get tags into the git mirror.

If you just want to build source tarballs at the tag, I'd recommend
using "svn export", as done in utils/release/export.sh.

Cheers,
Hans

Am 24.02.2016 um 14:07 schrieb Anton Korobeynikov via
llvm-dev:
> 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.
I wasn't aware that such a thing is even possible - isn't an SVN tag 
associated with a set of file at specific revisions that you can check out?
If yes, would it be possible to organize the LLVM workflow so that 
whenever a tag is placed, everything is checked out from SVN, checked 
into git, and tagged in git?

Regards,
Jo

On Wed, Feb 24, 2016 at 11:20 AM, Joachim Durchholz via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Am 24.02.2016 um 14:07 schrieb Anton Korobeynikov via llvm-dev:
>>
>> 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.
>
>
> I wasn't aware that such a thing is even possible - isn't an SVN
tag
> associated with a set of file at specific revisions that you can check out?
> If yes, would it be possible to organize the LLVM workflow so that whenever
> a tag is placed, everything is checked out from SVN, checked into git, and
> tagged in git?
In practice, the svn tags we make don't contain arbitrary content
though, they are a copy of the contents on the branch at a specific
revision, and there is a git hash corresponding to it - it would just
be pretty fiddly to hook this up, I expect.

Thanks,
Hans