[petsc-dev] petsc-dev on bitbucket

[Sean Farley]

>
> tags are no good. we implrement branches in different clones.
>

Which is not a better model.


> You could argue that we should throw away branches in clones have all
> clones in a single branch - and change our workflow.
>

Yes, I would suggest this.

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]


I think you are misusing the term "branch". Look at the repo for mercurial:

http://selenic.com/hg/tags

There are no other branches (just 'default' and 'stable'). Released
versions are just signed tags. This is what the mercurial community (e.g.
bitbucket's implementation) takes for the default. You don't need a fancy
prompt (but why *wouldn't* you want a fancy prompt??) to achieve this
workflow, just move the tag to the newest bugfix and be done with it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120209/6bbd3865/attachment.html>