<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Come on guys, it is completely moronic that bitbucket doesn't support subdirectories to hold repositories. No amount of rationalization can provide a reason for this absurdity.<br>
</blockquote><div><br></div><div>What's completely moronic is that petsc.cs.itt is hosting so many repositories that are mostly cruft:</div><div><br></div><div>Allen-Cahn-2D</div><div>Cahn-Hillard-1D</div><div>Cahn-Hillard-2D</div>
<div>FMM</div><div>FMM-dev</div><div>ams-dev</div><div>composing-nonlinear-solvers</div><div>cudaFMM</div><div><div>dft</div><div>dft-fft</div><div>dft-log</div><div>dft-mg</div><div>dft-rfd</div></div><div><div>externalpackages-old/MUMPS_4.7.3</div>
<div>externalpackages-old/MUMPS_4.9.2</div><div>externalpackages-old/ParMetis</div><div>externalpackages-old/ParMetis-3.1.1</div><div>externalpackages-old/SuperLU_4.0</div><div>externalpackages-old/SuperLU_DIST_2.2</div>
<div>
externalpackages-old/SuperLU_DIST_2.4</div><div>externalpackages-old/UMFPACK-5.2</div><div>externalpackages-old/f2cblaslapack</div><div>externalpackages-old/f2cblaslapack-3.1.1.q.old</div><div>externalpackages-old/fblaslapack</div>
<div>externalpackages-old/hypre-2.6.0b</div><div>externalpackages-old/sowing-1.1.11</div></div><div>lwang-dev</div><div>multiphysics</div><div>petsc-dev-new???</div><div>petscpathlib</div><div><div>pthread-paper</div><div>
reacting_flow</div><div>releases/BuildSystem-2.3.1</div><div>releases/BuildSystem-2.3.2</div><div>releases/BuildSystem-2.3.3</div><div>releases/BuildSystem-3.0.0</div><div>releases/BuildSystem-3.1</div></div><div><div>simpleConfigure</div>
<div>temp/petsc-dev-ts</div></div><div><br></div><div>If you look at the repositories left, only tutorials and externalpackages exist. We can even put the latter here:</div><div><br></div><div><a href="https://bitbucket.org/externalpackages" target="_blank">https://bitbucket.org/externalpackages</a></div>
<div><br></div><div>For the private paper repositories, bitbucket gives you an unlimited number of private repos for free.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Some of Jed's rationalizations are going off the deep end.<br></blockquote><div><br></div><div>Woah! That's the pot calling the kettle black.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* In order to not have a Releases directory he states: "I think separate clones for every release is clutter."<br></blockquote><div><br></div><div>You honestly think it's worth keeping repositories around that haven't been touched in 6 years? How is that not clutter?</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Face it, bitbucket has this really stupid feature.</blockquote>
<div><br></div><div>Funny, we say the same thing about your commit messages :-)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I see no upside to bitbucket and hence I only see a downside, so why change?</blockquote>
<div><br></div><div>Do you not remember getting burned by fail2ban while at the Utah (Nevada?) workshop?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Except Sean doesn't want to drag his ass over to IIT twice a year and people want to use buggy wireless networks.<br>
</blockquote><div><br></div><div>People! *None* of us would have to do *anything* to maintain the server. No more buying new hard drives, no more accidental shut-downs, *OTHER* people would fix that stuff.</div><div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tell me the real reason you want to use bitbucket.</blockquote><div><br></div><div>Just to upset you and then laugh when we see you pull your hair out. </div>
</div>