search for: e4303ba3

Displaying 3 results from an estimated 3 matches for "e4303ba3".

2016 Feb 25
1
RFC: Move the test-suite LLVM project to GitHub?
...> branches both locally and on GitHub. It's a lot of clerical work, and some > aspects of this all are easy to get wrong for a git newbie. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160225/e4303ba3/attachment.html>
2016 Feb 24
0
RFC: Move the test-suite LLVM project to GitHub?
Am 24.02.2016 um 21:57 schrieb Chandler Carruth via llvm-dev: > For all of these reasons, and also because I'd like to see how well (or > rather, how poorly) a service like GitHub actually works for the project, > it seems like splitting the test-suite out of the current subversion > repository and moving it there is the right call. My experience from a few years of contributing
2016 Feb 24
21
RFC: Move the test-suite LLVM project to GitHub?
Subject kinda says it all. Here is my rationale: The test-suite is really weird relative to the rest of the LLVM project: 1) It contains all manner of crazily licensed code. 2) We don't really care about the history at all. Any concerns around linear history or bisection are pretty much irrelevant. 3) We don't ever plan to have LLVM code move into or out from the test-suite 4) Its already