Update dist

[GetContented]

Re-grunted to update the dist folder

[azirbel]

@JulianLeviston could you explain how you built these changed files? It looks like our dist folder is inconsistent with master, but when I checkout master and run grunt I seem to get a different diff than what you've posted here. Could be a mistake on my end though.

[GetContented]

Oh yeah sure. Sorry :) I just forked, cloned my fork to my mac book pro, ran grunt and stopped it when it said "running task wait". Then I committed and pushed then created the pr. Seemed pretty standard. Hope I did it right?

Sent from my self advertising device

On 24 Mar 2014, at 7:03 pm, Alex Zirbel notifications@github.com wrote:

@JulianLeviston could you explain how you built these changed files? It looks like our dist folder is inconsistent with master, but when I checkout master and run grunt I seem to get a different diff than what you've posted here. Could be a mistake on my end though.

�
Reply to this email directly or view it on GitHub.

[azirbel]

Hey @JulianLeviston, sorry for being so slow on this.

Weird stuff! I haven't been able to find out why you get different results yet, but:

• If I clone out your fork of the repo, then git checkout HEAD~1, npm install & grunt, then I get the same diff you have submitted here.
  • If I check out our repo master, git clean -dfx, npm install & grunt, then I get a different diff.

Having a diff at all is a problem and needs fixing no matter what. But first I'd like to figure out why you get something different. Any ideas?

[GetContented]

Hehe actually I don't have any ideas, unfortunately :( You should use your own, tho... I was just doing it to save someone some work.

[azirbel]

Ok. I appreciate it - thank you! I think #106 is going out soon, so we'll update dist as part of that. It's not the best situation to be in, but for now I think the solution is to just be more consistent about updating dist with every PR.