<p dir="ltr">I personally find git (and its branches) rather cumbersome and wish libmesh used mercurial instead :-) <br>
And if hgsubversion actually worked there would no need for git :-)</p>
<p dir="ltr">Dmitry</p>
<div class="gmail_quote">On Jan 9, 2013 7:17 PM, "Jed Brown" <<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@mcs.anl.gov</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Libmesh just moved to github as well.<div><br></div><div>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]:</div>
<div><br></div><div>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></div><div><br></div><div>Fortunately, his project "gitifyhg" is now usable. [2]</div>
<div><br></div><div>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).</div>
<div><br></div><div>
[1] <a href="http://archlinux.me/dusty/2012/12/18/four-ways-to-do-local-lightweight-git-style-branches-in-mercurial/" target="_blank">http://archlinux.me/dusty/2012/12/18/four-ways-to-do-local-lightweight-git-style-branches-in-mercurial/</a><br>
</div><div>[2] <a href="http://archlinux.me/dusty/2013/01/06/gitifyhg-rewritten/" target="_blank">http://archlinux.me/dusty/2013/01/06/gitifyhg-rewritten/</a></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jan 9, 2013 at 5:48 PM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><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>
<span><font color="#888888"><br>
Barry<br>
</font></span><div><div><br>
On Jan 8, 2013, at 6:38 PM, Jed Brown <<a href="mailto:jedbrown@mcs.anl.gov" target="_blank">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" target="_blank">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" target="_blank">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" target="_blank">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" target="_blank">http://git.mpich.org/mpich.git</a> and git://<a href="http://git.mpich.org/mpich.git" target="_blank">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" target="_blank">devel@mpich.org</a> or <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a> for assistance.<br>
><br>
> Regards,<br>
> The MPICH Team<br>
> _______________________________________________<br>
> discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>
> To manage subscription options or unsubscribe:<br>
> <a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
><br>
<br>
</div></div></blockquote></div><br></div></div>
</blockquote></div>