New pin motion.base-feedrate in master branch

I think the runtest fails should be fixed before getting too far ahead, they obviously indicate a problem/problems somewhere.

phillc54 wrote: I think the runtest fails should be fixed before getting too far ahead, they obviously indicate a problem/problems somewhere.

Seems Issues $134, #177 and #283 refer. I think Andy is on the job as #283 was committed 19 hours ago to the official state-tags branch. The notes in the first test says it will be fixed by release of State tags and referred to #134. Talk about going around in circles for years!

Well I tried a rverse-feedcode-2.8 mix branch and it seems to have worked ok.
I's like to discuss if that's a tolerable idea - but I think Andy is the only other developer to talk to about this ...
usually I would discuss this on the mail list (where it should be).

Chris

Lets take it to the dev list. Perhaps Zultron will chip in?

andypugh wrote: Lets take it to the dev list. Perhaps Zultron will chip in?

Thanks Andy. There seems to be no reason why reverse run can't be pushed back to 2.8 as its been in master branch for over 12 months so its probably the most extensively tested new feature ever suggested for release.