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.. Satish
