<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear Chandler,<br>
<br>
First, can you articulate why you want to move the test suite to
Github? Is it taking up too much space, or is there some other
problem that you're trying to solve? I think you clearly explain
why moving the revision history isn't necessary, but it's not
clear to me what problem you are trying to solve.<br>
<br>
Second, if we move the revision history to Github, it would be
nice to archive the existing Subversion history somewhere (e.g.,
leave it on llvm.org but disable commit access to it). The test
suite has been used in numerous research papers, so keeping the
revision history around is good practice. We should only delete
the Subversion revision history if keeping it around is just too
onerous.<br>
<br>
Third, I assume your plan is to continue to track changes on
Github. Is that correct?<br>
<br>
As long as there's a good reason to do it and the existing
Subversion history isn't deleted, I don't see a problem with the
change.<br>
<br>
Regards,<br>
<br>
John Criswell<br>
<br>
<br>
On 2/24/16 3:57 PM, Chandler Carruth via llvm-dev wrote:<br>
</div>
<blockquote
cite="mid:CAARZr-PXc1KnUv1NXvJouUU8FrtHhy+LEf=gwVMM_bts19cypA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">Subject kinda says it all. Here is my rationale:
<div><br>
</div>
<div>The test-suite is really weird relative to the rest of the
LLVM project:</div>
<div>1) It contains all manner of crazily licensed code.<br>
</div>
<div>2) We don't really care about the history at all. Any
concerns around linear history or bisection are pretty much
irrelevant.</div>
<div>3) We don't ever plan to have LLVM code move into or out
from the test-suite</div>
<div>4) Its already big, and really should be much bigger. We
shouldn't have incentives to keep stuff out of the test suite
because of size, hosting cost, or anything else.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>When I chatted with folks on the board, this made sense to
them as well, and I've made sure we have a reasonable LLVM
organization set up on GitHub and all the board members are on
it: <a moz-do-not-send="true" href="https://github.com/llvm">https://github.com/llvm</a>
(I think only my membership is public at the moment).</div>
<div><br>
</div>
<div>There is still plenty to figure out about how to manage
this on github, but before doing anything else I just wanted
to shoot an email and see if folks like this idea.</div>
<div><br>
</div>
<div>Thanks!</div>
<div>-Chandler</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
John Criswell
Assistant Professor
Department of Computer Science, University of Rochester
<a class="moz-txt-link-freetext" href="http://www.cs.rochester.edu/u/criswell">http://www.cs.rochester.edu/u/criswell</a></pre>
</body>
</html>