[petsc-dev] close ts-fixes branch?

[Jed Brown]

On Thu, 25 Mar 2010 15:38:00 -0300, Lisandro Dalcin <dalcinl at gmail.com> wrote:
> On 25 March 2010 13:03, Satish Balay <balay at mcs.anl.gov> wrote:
> > On Thu, 25 Mar 2010, Lisandro Dalcin wrote:
> >
> >> 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.
> >
> > yes - we use clones as branch model [even for releases] - and should
> > avoid in-repo branches..
> >
> 
> Any way to COMPLETELY prune a in-repo branch? Unlikely, right?

The branch is written into the changeset, so if you edit history to
remove the "branch" tag, you change the checksum.  The mercurial people
say this is a feature, but I don't buy it.

Jed