[llvm-dev] Tags for releases in the monorepo

[NAKAMURA Takumi via llvm-dev]

I am tagging them manually.

The reason: I tried to rename release_600, but it caused a problem on
Windows, (possibly case-insensitive filesystem). Then I rewound it.

I will try renaming them in the next week. Please be patient.

On Sat, Oct 6, 2018 at 3:26 PM Bruce Hoult via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> +1
>
> On Fri, Oct 5, 2018 at 3:19 PM, Louis Dionne via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hi,
>>
>> I'm using the monorepo layout, and I can see the following tags
>> representing past releases of LLVM:
>>
>>     $ git tag -l
>>     RELEASE_400/final
>>     RELEASE_401/final
>>     RELEASE_500/final
>>     RELEASE_501/final
>>     RELEASE_700/final
>>     RELEASE_700/rc1
>>     RELEASE_700/rc2
>>     RELEASE_700/rc3
>>     prerelease_20180108
>>     release_600
>>     release_601
>>
>> I'm wondering why the tags for release 6.0.0 and 6.0.1 have a different
>> format than the tags for other releases. Is it just an oversight? Would it
>> be possible to add tags for the releases with the usual format? This
>> inconsistency makes it harder to script against the monorepo.
>>
>> Thanks,
>> Louis
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181006/ea69be67/attachment.html>