[myhdl-list] Named branches in repository

[Jan D. <ja...@ja...>]

As announced, I am now using named branches in the repository.

They implement different development lines with different
policies. Currently I use them to separate "bleeding edge"
development on the default branch from bug fixes for 0.6
in branch 0.6-maint. Merges occur only in one direction,
from 0.6-maint to default.

The alternative would have been different repositories,
which is the principal method advocated in the mercurial
documentation. Named branches are "advanced" but I
prefer them because you can switch development lines
without changes to your python setup.

I have documented this on the website:\

http://www.myhdl.org/doku.php/dev:repo#named_branches


-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
    Python as a HDL: http://www.myhdl.org
    VHDL development, the modern way: http://www.sigasi.com
    Analog design automation: http://www.mephisto-da.com
    World-class digital design: http://www.easics.com