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." -Hazen ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
