On Thu, Feb 9, 2012 at 8:26 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> On Wed, 8 Feb 2012, Sean Farley wrote: > > > > > > > Hell, if you *really* want to, just create the account: > petsc-release(s) > > > then the URL would be > > > > > > http://bitbucket.org/petsc-release/petsc-3.1 > > > > > > > Actually, it's even easier than that: > > > > https://bitbucket.org/petsc/petsc-dev/downloads > > > > which provides downloads for all taged changesets. > > tags are no good. we implrement branches in different clones. > I am not sure what you mean by this. Let me be explicit. This organization is semantic, and Completely outside the version control structure. I want something to tell me "this repo is about simulating rockets" like Kit, the voice in Michael's car. Tags are fine for this. So is a hierarchy. So is silly XML metadata. Matt > You could argue that we should throw away branches in clones have all > clones in a single branch - and change our workflow. > > But I think this will be too confusing to most of us [yeah you could > change your bash prompt to always indicate wich branch you are on - > wich is equivalent to 'cd different clone' - but not all of us are > that sophisticated] > > Satish > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120209/ce97da1b/attachment.html>
