[petsc-dev] [mpich-discuss] MPICH migration to git

[Jed Brown]

On Wed, Jan 9, 2013 at 10:08 PM, Sean Farley
<sean.michael.farley at gmail.com>wrote:

> There has historically been only one branching model … ever.
>

They have one thing they call a branch, another thing they call a bookmark,
another thing they call mq... They're all taking different approaches to
mostly-overlapping problems. Git has exactly one thing, which they call
"branch", that covers the whole gammut and is part of the base system (not
an extension) since day 1.


> What git
> invented was the concept of a bookmark and called it a 'branch'. It's
> a placeholder that isn't permanently written into the changeset.
>

The data model of hg bookmarks is equivalent to git branches. The
difference is (a) integration with the rest of the system and (b) bookmarks
are fragile in somewhat deep ways that Hg does not appear interested in
fixing "because that decision was made a long time ago".


>
> > As for consensus shifting towards git, I know only a few people that have
> > used both seriously and still prefer Hg. Meanwhile, there are a ton of
> > serious Python folks that prefer git (Lisandro, Andy Terrel, SciPy,
> NumPy,
> > PyClaw, etc).
>
> And how many of these people / projects have been influenced by you?
> All the ones you listed (mpich, lib mesh, Lisandro, Andy Terrel,
> SciPy, NumPy,  and PyClaw) seem to have spent time with you and your
> git-is-the-only-way model.
>

You give me *way* too much credit. ;-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130109/0990fed5/attachment.html>