fenics team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

I haven't seen it, but "free for open source" sounds dangerous...

/Anders


On Fri, Jun 09, 2006 at 03:22:20PM -0400, tomtzigt wrote:
> And from left field..... I love Perforce!
> 
> Perforce branch and merge is like a walk in the park.... Interactive
> resolves on demand too. Worth it even if you have to pay for it. Free for
> open source.
> 
> I have PETSc and FEniCS as code drops in the Perforce tree and a build
> script from the tar ball so that all can pull from Perforce and get all the
> software they need. Both PETSc and FEniCS are solid so we don't need to do
> any mods in our own sccs.
> 
> Theo
> 
> P.S. I do not work for Perforce Software and do not have an affiliation or
> stock position. I do like them though...
> 
> -----Original Message-----
> From: Anders Logg [mailto:logg@xxxxxxxxx] 
> Sent: Friday, June 09, 2006 3:02 PM
> To: Matthew Knepley
> Cc: Anders Logg; tomtzigt; Discussion of FEniCS development
> Subject: Re: [fenics-dev] Sieve
> 
> On Fri, Jun 09, 2006 at 01:43:27PM -0500, Matthew Knepley wrote:
> > On 6/9/06, Anders Logg <logg@xxxxxxxxx> wrote:
> > 
> >     Cool. How's Mercurial working out so far? Have you had any problems
> >     with it?
> > 
> >     /Anders
> > 
> > 
> > I like it. Its not as nice as BK, but workable. The problems are almost
> all
> > related to lack of bundling of operations. For instance, I always have to
> > do:
> > 
> >   hg pull
> >   hg update -m
> >   hg commit
> > 
> > instead of the BK model where it all happens correctly in sequence.
> > 
> >    Matt
> 
> I often end up with
> 
>     hg commit
>     hg push default
>     Aargh, someone beat me to it so I need to pull
>     hg undo
>     hg pull
>     hg update
>     Aargh, forgot -m
>     hg update -m
>     hg commit
>     hg push default
> 
> :-)
> 
> /Anders
> 
> 
>