Re: [3.6 Release] Release Candidate 2 available

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [3.6 Release] Release Candidate 2 available

Sedat Dilek
On Mon, Feb 9, 2015 at 9:47 PM, Anton Korobeynikov
<[hidden email]> wrote:

> Hans,
>
>>> I see a Git branch "release_36", but what has v3.6.0rc2 for a
>>> commit-id, can you tags that?
>>> No, there are no tags at all @ github.
>>
>> Anton, is it possible to translate the svn tags to git tags?
> In the past we had problems with git-svn tags, so we decided to go
> with branches only.
>

[ Following "[LLVMdev] [3.6 Release] RC4 has been tagged" thread on LLVMdev ML ]


Can you describe these problems?
If you cannot solve them by yourself, did/can you ask on Git mailing-list?

Why are there no more "svn-tags/RELEASE_NN" tags on GitHub-mirrors?
The last I see is "svn-tags/RELEASE_32".
So, this seems to have worked someday.

So I see a "final" tag for "RELEASE_360" in SVN.
Can you please do generate "svn-tags/RELEASE_360" tags for Git
accordingly (for llvm | cfe | compiler-rt | ...)?
If you cannot do, which are the last git-sha1-commit-ids for llvm |
cfe | compiler-rt (svn-revs see below)?

In conclusion:
Why are people using Git disadvantaged?

For now I waited for official tarballs.

Thanks in advance.

- Sedat -

[1] http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_360/final/ <---
Revision 230740
[2] http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_360/final/ <---
Revision 230741
[3] http://llvm.org/svn/llvm-project/compiler-rt/tags/RELEASE_360/final/
<--- Revision 230741
_______________________________________________
LLVM Developers mailing list
[hidden email]         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Reply | Threaded
Open this post in threaded view
|

Re: [3.6 Release] Release Candidate 2 available

Anton Korobeynikov-2
> In conclusion:
> Why are people using Git disadvantaged?
Short answer: because of git-svn and differences between what is a tag
in git and svn.

Long answer: git-svn never created proper git tags. Instead, it
converted svn tags to branches (because technically branches and tags
are same in svn). These branches were orphan and not usable for bunch
of things (I believe Takumi can provide a lot of of examples).
Therefore they were omitted from git mirror. Even more, we're using
the tagging scheme with release candidates and final  which is
incompatible with the way git-svn expects the stuff.

Therefore we decided to keep release branches only in the mirror.

> For now I waited for official tarballs.
You can always pull from release branches

--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
_______________________________________________
LLVM Developers mailing list
[hidden email]         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Reply | Threaded
Open this post in threaded view
|

Re: [3.6 Release] Release Candidate 2 available

Sedat Dilek
On Fri, Feb 27, 2015 at 11:33 AM, Anton Korobeynikov
<[hidden email]> wrote:

>> In conclusion:
>> Why are people using Git disadvantaged?
> Short answer: because of git-svn and differences between what is a tag
> in git and svn.
>
> Long answer: git-svn never created proper git tags. Instead, it
> converted svn tags to branches (because technically branches and tags
> are same in svn). These branches were orphan and not usable for bunch
> of things (I believe Takumi can provide a lot of of examples).
> Therefore they were omitted from git mirror. Even more, we're using
> the tagging scheme with release candidates and final  which is
> incompatible with the way git-svn expects the stuff.
>
> Therefore we decided to keep release branches only in the mirror.
>
>> For now I waited for official tarballs.
> You can always pull from release branches
>

Hi,

[ svn-tagging vs. git-tagging ]

( I use subversion to checkout from SVN mirrors, but not in my daily
working life. )
( I cloned llvm.git | clang.git | compiler-rt.git and archived them. )
( I do not want to checkout all 3 from SVN mirrors to have everything double. )

Isn't the problem caused from somewhere else?

Looking through [1]..[3]... Here llvm/svn-tag from [1]:
...
URL: http://llvm.org/viewvc/llvm-project?rev=230433&view=rev
Log:
Creating release candidate final from release_360 branch

Added:
    llvm/tags/RELEASE_360/final/   (props changed)
      - copied from r230432, llvm/branches/release_36/
...

So, you have a "rev=230433" referencing "what-ever-you-call-it"
"upper" "llvm-project".
Maybe I am thinking more in Git syntax, but why don't you tag within llvm-svn?
So, within llvm.git#release_36 branch I do not see any "230433" svn-rev.

$ cd ~/src/llvm-toolchain/llvm-git/

$ git branch
  master
* release_36

$ git log -10 | grep git-svn
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@230431
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@230346
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@230287
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@230284
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@230282
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@230281
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@230277
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@229874
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@229800
91177308-0d34-0410-b5e6-96231b3b80d8
    git-svn-id:
https://llvm.org/svn/llvm-project/llvm/branches/release_36@229757
91177308-0d34-0410-b5e6-96231b3b80d8

So, what shall I do... git-tag a "final" myself?


[ llvm-toolchain $version ]

So if I build from <{llvm|clang|compiler-rt}.git#release_36>, what
$version will I get?

   clang version 3.6.0 (tags/RELEASE_360/final)

Where (file) is the version bumped?

Here is the output of my clang built from official v3.6.0rc4 tarballs:

# LC_ALL=C clang -v
clang version 3.6.0 (tags/RELEASE_360/rc4)
Target: x86_64-unknown-linux-gnu
Thread model: posix
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.2
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64

Currently, I decided to wait for the official "final" tarballs.

- Sedat -

[1] http://lists.cs.uiuc.edu/pipermail/llvm-branch-commits/2015-February/008783.html
[2] http://lists.cs.uiuc.edu/pipermail/llvm-branch-commits/2015-February/008784.html
[3] http://lists.cs.uiuc.edu/pipermail/llvm-branch-commits/2015-February/008785.html
_______________________________________________
LLVM Developers mailing list
[hidden email]         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev