Displaying 2 results from an estimated 2 matches for "1f81e888".
Did you mean:
15813888
2018 Jan 03
0
Distinguishing trunk version number from release
...lman/listinfo/llvm-dev
--
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180103/1f81e888/attachment.html>
2018 Jan 03
2
Distinguishing trunk version number from release
On 01/03/2018 11:25 AM, James Y Knight via llvm-dev wrote:
> On Wed, Jan 3, 2018 at 12:24 PM, James Y Knight <jyknight at google.com
> <mailto:jyknight at google.com>> wrote:
>
> I'd like to propose that trunk always have a version number which
> is in between versions used by the previous release branch, and
> before the versions used in the next