<p dir="ltr"><br>
On Jan 9, 2013 10:13 PM, "Barry Smith" <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
><br>
><br>
> On Jan 9, 2013, at 10:03 PM, Dmitry Karpeev <<a href="mailto:karpeev@mcs.anl.gov">karpeev@mcs.anl.gov</a>> wrote:<br>
><br>
> ><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>
> > > Then I would consider switching over to git and proceeding to make fun of hg users,<br>
> > Is this the only reason to switch?<br>
><br>
> Yes, making fun of other people is the highest priority.<br>
><br>
> > 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.<br>
><br>
> Sorry I was not clear. ___I____ want to be able to continue with my simple-minded work flow and have it be compatible with what other people do. It is fine if Jed and Karl and Matt and whoever uses all kinds of cool Git features so long as it doesn't make ___my___ workflow too intellectually difficult for me. That is I only object to the change if it requires always wrestling with several new concepts that don't exist in Hg. I do<br>
><br>
> hg clone<br>
> hg pull<br>
> hg commit<br>
> hg merge<br>
> hg push<br>
><br>
> I want to be able to do something similar with git; I don't want new __required__ things introduced like<br>
><br>
> git sanitize x y z<br>
><br>
> where x y z are particular changing options that I HAVE to magically know what they are each time and get right or I fuck myself over. Which did happen the one time I tried to use one of Jed's git repositories when it won't let me push because I hadn't indicated the right branch or some such shit. That is I don't want the repository system to require __me__ to keep in my brain any state information that I need to convey to the repository when interacting with it each time.<br>
I think the presence of the index will be the biggest curveball for you.<br>
><br>
> Barry<br>
><br>
><br>
><br>
><br>
> Barry<br>
><br>
> ><br>
> > Dmitry<br>
> ><br>
> > ><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>
><br>
</p>