On 2014-08-13 10:28-0400 Hazen Babcock wrote: > > Sending this to a wider audience. In short, PLplot is now using git for > version control. > > http://sourceforge.net/p/plplot/plplot/ci/master/tree/ > > -Hazen > > -------- Original Message -------- > Subject: Re: [Plplot-core] git conversion status > Date: Tue, 12 Aug 2014 16:24:27 -0400 > From: Hazen Babcock <hbabc...@mac.com> > To: plplot-c...@lists.sourceforge.net > > On 8/11/2014 6:47 PM, Hazen Babcock wrote: >> >> If there are no additional commits between today and tomorrow I'll clone >> this to SF and change the SVN repo to read-only. > > All set now. Our SVN repository is (or should be) read-only under the > "Old Code" tab. Our new git repository is available under the "Code" tab. > > Two initial suggestions: > 1. Like github, SF is displaying the README.txt file. This appears to > have last been modified in 2007. Maybe this should be the same as > README.release? Or maybe it should be updated? > > 2. Clean up the repository by pruning off all the branches. Don't worry > they'll still be there if you really want to look at them (as described > here): > > http://stackoverflow.com/questions/3640764/can-i-recover-branch-after-the-deletion-in-git > > Many projects that I have seen only have a master branch in their > release repository.
Many thanks, Hazen, for pushing this conversion project to completion. > [Suggestions] 2. Clean up the repository by pruning off all the branches. Don't worry > they'll still be there. >From my very recent first read of the Chapter on branching in "Pro Git" (<http://git-scm.com/book> and highly recommended), it appears git branches are extremely light-weight and simply point to a particular snapshot in the repository, and that chapter also confirms what you said about removing a branch does not remove the snapshot. > if you really want to look at them (as described > here): > > http://stackoverflow.com/questions/3640764/can-i-recover-branch-after-the-deletion-in-git That method does not seem fool-proof. See the expire subcommand for "git reflog". Furthermore, some of the PLplot branches are still active (e.g., test_cmake) and useful even though I will likely never want to merge that material to the master branch. So I would prefer branches not be deleted if they are active (test_cmake and perhaps others), and for the ones we decide to delete, I would like some permanent record of the branch that would allow us to reliably resurrect it again. My impression is you cannot delete tags. If that is true, could we make a specially named tag, e.g., branch_AM-LT for the tip of the currently existing AM-LT branch before deleting that branch? And then afterward be able to reliably resurrect the branch using that tag to access the last commit corresponding to the (old, deleted) branch head? And so on for the other branches we wish to delete? (Sorry that questions about policy for our git repo keep getting conflated with questions about git capabilities, but we are likely to be stuck with such conflation for quite a while until more of us become git experts.) Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
