<div dir="ltr">On Tue, Mar 12, 2013 at 5:09 PM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Mar 12, 2013, at 4:01 PM, Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> wrote:<br>
<br>
> On Tue, Mar 12, 2013 at 4:48 PM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
><br>
> On Mar 12, 2013, at 3:42 PM, Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> wrote:<br>
><br>
> > On Tue, Mar 12, 2013 at 4:30 PM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
> ><br>
> > On Mar 12, 2013, at 2:52 PM, Karl Rupp <<a href="mailto:rupp@mcs.anl.gov">rupp@mcs.anl.gov</a>> wrote:<br>
> ><br>
> > > Hi Richard,<br>
> > ><br>
> > > Jed and I set up detailed instructions on how to use Git and Mercurial:<br>
> > > <a href="https://bitbucket.org/petsc/petsc/wiki/Home" target="_blank">https://bitbucket.org/petsc/petsc/wiki/Home</a><br>
> ><br>
> > Note that both Karl and Jed know git very well, so these pages will pretty much suck for new users.<br>
> ><br>
> > I agree. That is why its important that its a Wiki.<br>
><br>
> Because you perceive a Wiki as something that is very easy to change something in quickly. I think in that sense Wikis are like PERL, it is very quick to put something together that looks powerful, but long term maintenance and general extension is impossible. Why not put all PETSc source code into the wiki then we can easily edit it without bothering with Emacs and shells?<br>
><br>
> I think Wikis are good because the build system is right there. No monkeying with LaTeX+latex2html/Sphinx/DocBook/WhatEverCrazySystem. I can see exactly what I put in right away, and so can everyone else. Its exactly the same version control as the source, as Jed pointed out, and I have been using them for other projects and its easy.<br>
><br>
> I think using one system for a manual (LaTeX) and one system for online help (Wiki) is fine. In fact, the brain trust at PETSc Central<br>
> already does this since we have a FAQ and Function Manpages separate from our manual.<br>
><br>
> I am fine with putting that stuff there in the short term, but how about in the longer term having it as a subtree (subrepo?) in the petsc/src/docs/ directory?<br>
><br>
> Why would this be any different?<br>
<br>
</div> Barry has an extremely crappy memory and if he cannot find it in the petsc.git tree he cannot find it. It is difficult for Barry to handle: some stuff is here, some stuff is here, some stuff is over there (this should be obvious with my obsession with constantly organizing the PETSc tree). This was not true with Barry 20 years ago but is now and will be for you in 20 years :-)</blockquote>
<div><br></div><div style>I feel the impending forgetfulness as a shadow across my back. I think its also possible I will become cranky.</div><div style><br></div><div style>What if we make the Wiki repository a subtree of PETSc, just like BuildSystem? I read all the stuff Jed sent on</div>
<div style>this and it looks like exactly what we wanted.</div><div style><br></div><div style> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Barry<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> Matt<br>
><br>
><br>
> Barry<br>
><br>
> > I checked one thing in this morning.<br>
> ><br>
> > Matt<br>
> ><br>
> ><br>
> > Barry<br>
> ><br>
> > ><br>
> > > In short, to get your changes merged back 'upstream', you still just need to send a pull request for petsc-hg on Bitbucket. :-)<br>
> > ><br>
> > > Best regards,<br>
> > > Karli<br>
> > ><br>
> > ><br>
> > ><br>
> > > On 03/12/2013 02:42 PM, Richard Tran Mills wrote:<br>
> > >> Hi Barry,<br>
> > >><br>
> > >> I will start using Git for working with petsc-dev when there are some<br>
> > >> clear instructions on the workflow we should be using. In the meantime<br>
> > >> I have some petsc-dev tasks on my to-do list and I plan to work using a<br>
> > >> fork of petsc-hg. To get my changes merged back "upstream", I assume I<br>
> > >> still just need to submit a pull request for petsc-hg on BitBucket?<br>
> > >><br>
> > >> Thanks,<br>
> > >> Richard<br>
> > >><br>
> > >> On 3/12/13 12:16 PM, Barry Smith wrote:<br>
> > >>><br>
> > >>> PETSc dev users,<br>
> > >>><br>
> > >>> The PETSc repositories have been moved. They are at<br>
> > >>><br>
> > >>> https::/<a href="http://bitbucket.org/petsc/petsc" target="_blank">bitbucket.org/petsc/petsc</a> <<a href="http://bitbucket.org/petsc/petsc" target="_blank">http://bitbucket.org/petsc/petsc</a>><br>
> > >>> (git version)<br>
> > >>> https:/<a href="http://bitbucket.org/petsc/petsc-hg" target="_blank">bitbucket.org/petsc/petsc-hg</a><br>
> > >>> <<a href="http://bitbucket.org/petsc/petsc-hg" target="_blank">http://bitbucket.org/petsc/petsc-hg</a>> (Mecurial version)<br>
> > >>><br>
> > >>> please reclone all your repositories and do not use the previous<br>
> > >>> repository!<br>
> > >>><br>
> > >>> You may make pull requests via bitbucket for either repository. The<br>
> > >>> Mecurial version is read only; active developers with write access<br>
> > >>> will be working with the git version but the the Mecurial version will<br>
> > >>> always be in sync with the master branch of the git version.<br>
> > >>><br>
> > >>> Problems? Send email or bug one of Jed, Satish, Barry<br>
> > >>><br>
> > >>> Barry<br>
> > >>><br>
> > >>><br>
> > >>> Begin forwarded message:<br>
> > >>><br>
> > >>>> *From: *Jed Brown <<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@mcs.anl.gov</a> <mailto:<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@mcs.anl.gov</a>>><br>
> > >>>> *Subject: **petsc-hg*<br>
> > >>>> *Date: *March 12, 2013 10:20:51 AM CDT<br>
> > >>>> *To: *Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a> <mailto:<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>>><br>
> > >>>><br>
> > >>>> <a href="https://bitbucket.org/petsc/petsc-hg/" target="_blank">https://bitbucket.org/petsc/petsc-hg/</a><br>
> > >>>><br>
> > >>>> This is currently writable only by me. It will mirror 'master' from<br>
> > >>>> the Git repo and people can send pull requests to it.<br>
> > >>><br>
> > >><br>
> > >><br>
> > >> --<br>
> > >> Richard Tran Mills, Ph.D.<br>
> > >> Computational Earth Scientist | Joint Assistant Professor<br>
> > >> Hydrogeochemical Dynamics Team | EECS and Earth & Planetary Sciences<br>
> > >> Oak Ridge National Laboratory | University of Tennessee, Knoxville<br>
> > >> <a href="mailto:E-mail%3Armills@ornl.gov">E-mail:rmills@ornl.gov</a> V: <a href="tel:865-241-3198" value="+18652413198">865-241-3198</a><a href="http://climate.ornl.gov/~rmills" target="_blank">http://climate.ornl.gov/~rmills</a><br>
> > >><br>
> > ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
> > -- Norbert Wiener<br>
><br>
><br>
><br>
><br>
> --<br>
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
> -- Norbert Wiener<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener
</div></div>