Tags give the ability to mark specific points in history as being important
- Sort by
- Name
- Oldest updated
- Last updated
-
llvmorg-8.0.1-rc1 Creating release candidate rc1 from release_801 branch llvm-svn: 360979
-
llvmorg-8.0.1-rc2 Creating release candidate rc2 from release_801 branch llvm-svn: 363031
-
llvmorg-8.0.1-rc3 Creating release candidate rc3 from release_801 branch llvm-svn: 364604
-
llvmorg-8.0.1 Creating release candidate final from release_801 branch llvm-svn: 366581
-
llvmorg-8.0.1-rc4 Creating release candidate rc4 from release_801 branch llvm-svn: 365728
-
llvmorg-10-init Tag the 10.0.0 version bump. The tag name, llvmorg-10-init, signifies that this is the initial commit with major version number 10. With this tag in place, git-describe can be used to generate nicer names for commits on master, for example: $ git describe <hash> llvmorg-10-init-<number>-g<hash> where <number> is the number of commits since this tag. The plan is to add this kind of tag together with future version bumps.
-
llvmorg-9.0.0-rc1 Creating release candidate rc1 from release_900 branch llvm-svn: 367223
-
llvmorg-9.0.0-rc2 Creating release candidate rc2 from release_900 branch llvm-svn: 368708
-
llvmorg-9.0.0-rc3 Creating release candidate rc3 from release_900 branch llvm-svn: 370469
-
llvmorg-9.0.0-rc4 Creating release candidate rc4 from release_900 branch llvm-svn: 371500
-
llvmorg-9.0.0-rc5 Creating release candidate rc5 from release_900 branch llvm-svn: 371837
-
llvmorg-9.0.0-rc6 Creating release candidate rc6 from release_900 branch llvm-svn: 372115
-
llvmorg-9.0.0 Creating release candidate final from release_900 branch llvm-svn: 372316
-
llvmorg-11-init Tag the 11.0.0 version bump.
-
llvmorg-10.0.0-rc1 Tag 10.0.0-rc1
-
llvmorg-10.0.0-rc2 Tag 10.0.0-rc2