<p dir="ltr"><br>
On Jan 9, 2013 9:51 PM, "Barry Smith" <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
><br>
><br>
> On Jan 9, 2013, at 7:17 PM, Jed Brown <<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@mcs.anl.gov</a>> wrote:<br>
><br>
> > Libmesh just moved to github as well.<br>
> ><br>
> > I think if you carefully consider the branching model, it has a clear advantage over everything else. Dusty Phillips put it nicely in his recent blog post [1]:<br>
> ><br>
> > Git branches are simple and elegant. Mercurial branches are… well, it depends what kind of branch you want. You do know what kind of branch you want, right?<br>
><br>
> Branches are the work of the devil and should be avoided at all cost :-)<br>
><br>
> ><br>
> > Fortunately, his project "gitifyhg" is now usable. [2]<br>
> ><br>
> > 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).<br>
> ><br>
> > [1] <a href="http://archlinux.me/dusty/2012/12/18/four-ways-to-do-local-lightweight-git-style-branches-in-mercurial/">http://archlinux.me/dusty/2012/12/18/four-ways-to-do-local-lightweight-git-style-branches-in-mercurial/</a><br>
> > [2] <a href="http://archlinux.me/dusty/2013/01/06/gitifyhg-rewritten/">http://archlinux.me/dusty/2013/01/06/gitifyhg-rewritten/</a><br>
> ><br>
><br>
> 1) If Satish and you can come up with (or point me to) a mapping from my current hg workflow (which is pretty dang simple-minded) to how I would do things correctly in Git (and I am satisfied with that mapping) and<br>
><br>
> 2) There is a way to translate our current hg repository to git without losing information and<br>
><br>
> 3) We can continue to use bitbucket more or less that same way as now (or is there a reason to shift to github and it has decent "project" support?)?<br>
><br>
> Then I would consider switching over to git and proceeding to make fun of hg users,<br>
Is this the only reason to switch? Since otherwise it would have to be equivalent to hg (as per your aforementioned requirements). Besides, currently there is no globally-visible use of branches in the petsc workflow, as far as I can tell. Finally, you would have to deal with the INDEX and the extra states that it implies.</p>
<p dir="ltr">Dmitry<br></p>
<p dir="ltr">><br>
> Barry<br>
><br>
> ><br>
> > On Wed, Jan 9, 2013 at 5:48 PM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
> ><br>
> > Yes but given their absolutely horrible decision to stick with SVN all these years I cannot trust their decision to go with GIT. Sadly this is a very big argument for NOT switching PETSc to GIT. This email is only partly in jest, it has a serious component as well: is the "everyone's switching to git" just a case of the sheeple following the latest new thing without a proper technical evaluation or is it a carefully thought out decision?<br>
> ><br>
> > Barry<br>
> ><br>
> > On Jan 8, 2013, at 6:38 PM, Jed Brown <<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@mcs.anl.gov</a>> wrote:<br>
> ><br>
> > > Everyone's doing it. ;-)<br>
> > ><br>
> > > ---------- Forwarded message ----------<br>
> > > From: Dave Goodell <<a href="mailto:goodell@mcs.anl.gov">goodell@mcs.anl.gov</a>><br>
> > > Date: Tue, Jan 8, 2013 at 6:23 PM<br>
> > > Subject: [mpich-discuss] MPICH migration to git<br>
> > > To: <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
> > ><br>
> > ><br>
> > > MPICH users & developers,<br>
> > ><br>
> > > The MPICH project has transitioned from using SVN as our version control system (VCS) to using git instead. Details of the switch are described here:<br>
> > ><br>
> > > <a href="http://wiki.mpich.org/mpich/index.php/Git">http://wiki.mpich.org/mpich/index.php/Git</a><br>
> > ><br>
> > > Highlights from the document and the transition:<br>
> > ><br>
> > > * Read-only git clones are available at <a href="http://git.mpich.org/mpich.git">http://git.mpich.org/mpich.git</a> and git://<a href="http://git.mpich.org/mpich.git">git.mpich.org/mpich.git</a><br>
> > > * All critical history from SVN has been imported into the git history.<br>
> > > * The SVN server and its associated history are not going away, although it has been made read-only.<br>
> > ><br>
> > > We continue to work through our documentation and automated processes (cron jobs, etc.) to update them to the new system. Our trac instance will transition to understand the new VCS soon, although it currently displays only historical SVN data.<br>
> > ><br>
> > > Please bear with us as we work through this transition period. If you have trouble with the new setup, please contact <a href="mailto:devel@mpich.org">devel@mpich.org</a> or <a href="mailto:discuss@mpich.org">discuss@mpich.org</a> for assistance.<br>
> > ><br>
> > > Regards,<br>
> > > The MPICH Team<br>
> > > _______________________________________________<br>
> > > discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
> > > To manage subscription options or unsubscribe:<br>
> > > <a href="https://lists.mpich.org/mailman/listinfo/discuss">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
> > ><br>
> ><br>
> ><br>
><br>
</p>