On 24 May 2013 15:38, Sebastian Kuzminsky <s...@highlab.com> wrote: > I object to changing it in 2.5, but i don't object to changing it in master > (if you test it and make sure none of the sample configs break).
I can't test every sample config, I don't have all the hardware. I can confirm that a gitweb grep indicates that the string "home-state" only exists in docs and the line of code that creates the parameter. > We're way too deep into the 2.5 release to change stuff like this. Pins and > parameters do behave differently, and while we may not have any configs that > care, we don't know what our users are doing. I can imagine (for example) > setups that use scripts to look at 'halcmd show', that would get confused if > axis.N.home-state moved from the Parameters list to the Pins list, so these > hypothetical users would be affected by the change. I see your point. I differ on the assessment of the risk:benefit ratio. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
