On Thu, Feb 9, 2012 at 20:59, Satish Balay <balay at mcs.anl.gov> wrote:
> If we have to create multiple accounts to better organize repos - so > be it.. > I take it the concern is that we end up with a long list of release repositories that would look like clutter (although they'll be sorted so they wouldn't be near the top). Looking at the history, we really only ever have one release repository that is accepting patches. After the 3.2 release, there are zero patches applied to petsc-3.1. So maybe it would make sense to just have a single "petsc-release" repository. You can update to tags if you want to revisit something old. Note that this would make our installation tutorials more future-proof, always clone petsc-release if you want the release. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120209/9b0d3d39/attachment.html>
