[petsc-dev] close ts-fixes branch?

Lisandro Dalcin dalcinl at gmail.com
Thu Mar 25 11:00:44 CDT 2010

On 25 March 2010 01:14, Kai Germaschewski <kai.germaschewski at unh.edu> wrote:
> Fine with me (I'm the one who introduced it originally).
> My off-topic 2 cents: I hate reply-to headers.

BTW, I think this is an example of bad usage of mercurial branches...
You should use a separate clone for these kind of tasks. Mercurial
branches would make more sense for release versus development,
although even PETSc does not uses this model. IMHO, creating a branch,
push some fixes, merge back to default, and close branch is just
repository pollution.

Lisandro Dalcin
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594

More information about the petsc-dev mailing list