On 2014-08-16 22:37-0400 Hazen Babcock wrote: > On 8/13/2014 3:16 PM, Alan W. Irwin wrote: >> On 2014-08-13 10:28-0400 Hazen Babcock wrote: >> >> >> 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. > > I've looked at this a little more and I'm not sure that I fully understand > the concern. You are worried that someone will run "git reflog expire" on the > master SF repo? It is not clear that to me that this is even possible. This > link would suggest not: > > http://stackoverflow.com/questions/17857723/whats-the-difference-between-git-reflog-and-log > > "git reflog doesn't traverse HEAD's ancestry at all. The reflog is an ordered > list of the commits that HEAD has pointed to: it's undo history for your > repo. The reflog isn't part of the repo itself (it's stored separately to the > commits themselves) and isn't included in pushes, fetches or clones; it's > purely local."
Hi Hazen: Thanks for looking further at reflog, but local doesn't sound like what I want since that would be a single point of failure (e.g., if I am keeping this information on my local disk repo, that disk could fail), and nobody could access that information other than me. Of course, you could choose that location as the SF repo, but then only certain privileged users can access that information via ssh and appropriate git commands. Also SF staff aperiodically change repo formats (as they did in the Allura conversion), and for such a mass conversion they might not even bother to keep the reflog info. Remember, my basic motivation is to allow access to our history by anybody that is interested in the future. Therefore, I far prefer to store the information in a file in the repo since that file is available to everyone, automatically backed up by everyone cloning it, and even in the unlikely event someone deletes that file in error you can still restore it from finding the parent of the associated commit in the log that deleted that file. (For git newbies here, see <http://stackoverflow.com/questions/953481/restore-a-deleted-file-in-a-git-repo>.) To make this file proposal concrete, I am suggesting storing the file in PLplot_repo_information/README_svn2git_conversion (a directory and name that are unlikely to be deleted by accident by anyone) that states the commands we used to do the conversion and test it (the contents of the AWIREADME file I sent you plus additional documentation of the subversion branches that were converted to git and then deleted with explicit instructions on how to resurrect each one of them). I think we should also store in that directory the 4 files we used for the conversion, i.e., the two files used with svn-all-fast-export, the convert tags bash script that was sourced, and my standalone bash script to test the results in that directory. Do you see git (or any other) issues with these ideas? If you forsee no obvious problems, then I will put this near the top of my git ToDo list to get rid of the historical subversion-style branches, and put resurrecting test_cmake and copying the test_ada subdirectory of that to a better location later in my ToDo list. 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
