[petsc-dev] petsc-dev on bitbucket

[Sean Farley]

>
> There is only a 1-level hierarchy based on a top level account. Sean
> created 'petsc' for our stuff. We can create many, so that
> we have 'petsc-release', 'petsc-private', etc. if we want. Of course, I
> want traditional hierarchy, and will file a feature request.
>

If you phrase it like that ("traditional hierarchy"), 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:

https://bitbucket.org/seanfarley/petsc-dev

The nice thing about this is that you can tell where it was forked from:
"(fork of petsc / petsc-dev)"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120208/94808ad7/attachment.html>