On 2014-09-23 03:30-0700 phil rosenberg wrote: > @Hazen and Alan > I think an email went AWOL from Hazen somewhere, but from Alan's reply I > guess it probably said that we should not be rebasing public branches. I must > confess that I think almost everything I have read about rebasing says do not > rebase a public branch. I'm certainly no expert, but it does make me nervous > that we are suggesting to fly in the face of the perceived wisdom. I think I > would be much more comfortable with accepting that where we need to > collaborate on things we and use public branches, we merge these instead of > rebasing them. I know this makes for a slightly less tidy history, but such > large changes don't happen often. Don't forget it isn't only us that can > download a public branch - anyone can download from my repo, find and fix a > bug, then make a push request - if we have to say sorry that history doesn't > exist we can't accept your push, then it doesn't make us look great. > That is of course a very idealistic way of looking at things and I'm all for > practicality over idealism. So if you still want to go for the rebase option > then I have no problem with that. Just so long as we have considered the > potential problems.
It appears e-mails are still going astray. For example, yesterday, I believe Hazen and I came to consensus on this list concerning this issue, and I wrote that consensus up as an additional paragraph in README.developers and asked for your and Hazen's comments on that paragraph. I believe that paragraph answers the concerns you expressed above, but please let me know if it doesn't. > [...]However I am certainly still open to suggestions - I think based on the other comments on this thread I will set up a github repository and people can see what I've done so far and comment and suggest as needed. See the remarks in README.developers concerning that possibility. 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 __________________________ ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
