On Wed, Feb 8, 2012 at 10:54 AM, Sean Farley <span dir="ltr">&lt;<a href="mailto:sean@mcs.anl.gov">sean@mcs.anl.gov</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div>There is only a 1-level hierarchy based on a top level account. Sean created &#39;petsc&#39; for our stuff. We can create many, so that</div>



<div>we have &#39;petsc-release&#39;, &#39;petsc-private&#39;, etc. if we want. Of course, I want traditional hierarchy, and will file a feature request.</div></div></blockquote><div><br></div></div><div>If you phrase it like that (&quot;traditional hierarchy&quot;), then it will fall on deaf ears. The most I could see them adding is a way to create repo groups based on user groups (which exist currently). If you want your own personal collection of repos right-fucking-now, then fork the repos you want into your own account, like so:</div>


<div><br></div><div><a href="https://bitbucket.org/seanfarley/petsc-dev" target="_blank">https://bitbucket.org/seanfarley/petsc-dev</a></div><div><br></div><div>The nice thing about this is that you can tell where it was forked from: &quot;(fork of petsc / petsc-dev)&quot;</div>


</div>
</blockquote></div><br>No I mean I want<div><br></div><div>  petsc/releases/petsc-3.1</div><div>  petsc/tools/parsing/BarrysNewHTMLMunger</div><div><br></div><div>    Matt<br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>
</div>