<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Mar 24, 2014 at 9:50 AM, Frank Loeffler <span dir="ltr"><<a href="mailto:knarf@cct.lsu.edu" target="_blank">knarf@cct.lsu.edu</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
See this as proposal. This essentially puts every thorn into its own<br>
repository, but combines:<br>
<br>
- PITTNullCode<br>
- GRHydro<br>
- CactusExamples<br>
- CactusTest<br>
- CactusWave<br>
<br>
It also leaves out ExternalLibraries, at least for now. When we are<br>
going to move to the proposed mechanism, these repositories would need<br>
to be created from scratch anyway.<br></blockquote><div><br></div><div>It's not important right now since the ExternalLibraries won't be transitioning yet, but while I think of it, it would be possible to maintain the history rather than creating the repository from scratch. This could be done using git filter-branch to remove the tarballs from the history and put them in a submodule instead. Checking out the out the thorn would then not get all the tarballs by default. Of course, if a tarball is needed then the entire history would have to be downloaded. However, if the ExternalLibraries eventually move to a system where the tarball is not included but instead fetched on demand, then the large history-of-tarballs repository would only have to be fetched when checking out an old version of the external library.</div>
</div></div></div>