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

Sean Farley sean.michael.farley at gmail.com
Wed Jan 9 23:01:44 CST 2013


On Wed, Jan 9, 2013 at 10:50 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> On Wed, Jan 9, 2013 at 10:39 PM, Sean Farley <sean.michael.farley at gmail.com>
> wrote:
>>
>> Well, first of all, mq is being deprecated. Matt Mackall wanted a
>> general solution that would work in the mercurial framework. That
>> solution is the changeset evolution concept. Once I started using that
>> workflow, I whole-heartedly agree that mq is a pain and I could never
>> go back.
>
>
> I'm glad to see they've changed their mind on this one. Recall that they
> were recommending mq for several years after it should have been deprecated.

Ok?

>> >> > 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. ;-)
>>
>> But what if these people had been shown how to use `hg evolve`
>> instead? Would they still have switched to git?
>
>
> Would you have used a 2012 Linux laptop if offered to you in 2000? Does that
> mean you want to ditch your mac now?

No, my mac works and doesn't look like crap. I have to stare at my
computer all day, so why am I the asshole for wanting it to look really
nice? Also, I don't want to recompile *anything* just to join a
wireless network. Recall both you (and even Peter, I believe) had to
do that within the last year or so.

> You should try selling fusion power and string theory while you're at it.
> ;-)
>
> Even Atlassian puts out blog posts advocating git (almost a year ago now):
> http://blogs.atlassian.com/2012/03/git-vs-mercurial-why-git/

Yes, Atlassian seems to have not gotten the memo about changeset
evolution. Sigh.



More information about the petsc-dev mailing list