llvm dev - Feb 2015 - [LLVMdev] [3.6 Release] Release Candidate 2 available

Hi,

is it possible to have appropriate tags for the Git repositories @ github?

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.

Can you add in your announces a svn-trunk revision next time (for rc3)?
Somehow it should be clear what is "rc2".

Thanks.

Regards,
- Sedat -

+Anton who manages the git mirror

On Sat, Feb 7, 2015 at 4:04 PM, Sedat Dilek <sedat.dilek at gmail.com>
wrote:
> Hi,
>
> is it possible to have appropriate tags for the Git repositories @ github?
>
> 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?
> Can you add in your announces a svn-trunk revision next time (for rc3)?
> Somehow it should be clear what is "rc2".
The authoritative source of information for the branch is the
llvm-branch-commits mailing list [1]. There you can find for example
the tagging of llvm for rc2 [2].

 - Hans

 1. http://lists.cs.uiuc.edu/mailman/listinfo/llvm-branch-commits
 2.
http://lists.cs.uiuc.edu/pipermail/llvm-branch-commits/2015-January/008644.html

On Mon, Feb 9, 2015 at 3:47 AM, Hans Wennborg <hans at chromium.org>
wrote:
> +Anton who manages the git mirror
>
> On Sat, Feb 7, 2015 at 4:04 PM, Sedat Dilek <sedat.dilek at
gmail.com> wrote:
>> Hi,
>>
>> is it possible to have appropriate tags for the Git repositories @
github?
>>
>> 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?
>
>> Can you add in your announces a svn-trunk revision next time (for rc3)?
>> Somehow it should be clear what is "rc2".
>
> The authoritative source of information for the branch is the
> llvm-branch-commits mailing list [1]. There you can find for example
> the tagging of llvm for rc2 [2].
>
Thanks for the clarification.
>From [2]:
...
URL: http://llvm.org/viewvc/llvm-project?rev=227650&view=rev
Log:
Creating release candidate rc2 from release_360 branch
...

Can you mention the "rev" in your next announce emails (see [1], the
announce of v3.6.0rc2)?

- Sedat -

[1] http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-February/081677.html
>  - Hans
>
>  1. http://lists.cs.uiuc.edu/mailman/listinfo/llvm-branch-commits
>  2.
http://lists.cs.uiuc.edu/pipermail/llvm-branch-commits/2015-January/008644.html

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.

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