[petsc-dev] petsc branching methodology?

Jed Brown jed at jedbrown.org
Mon Nov 2 15:54:47 CST 2015

JR Cary <cary at txcorp.com> writes:

> Oh.  Good thing that workflow is called "simplified" or
> I might not have known!


gitworkflows(7) also discusses a true throw-away branch called "pu"
(proposed updates) that is convenient for some projects, but difficult
to manage with decentralized integration (multiple integrators versus a
single integrator at the top) and complicated to explain to
user/developers wondering what branch to use if they want to try the
bleeding edge.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20151102/4af88de8/attachment.sig>

More information about the petsc-dev mailing list