> Presentation Final Final [2].pdf
Alexey - please make sure to use 'Copy of Presentation Final Final [2] (Matt's version) (Copy).pdf' going forward. Presentation Final Final [2].pdf is out of date.
Thx.
Alexey - please make sure to use 'Copy of Presentation Final Final [2] (Matt's version) (Copy).pdf' going forward. Presentation Final Final [2].pdf is out of date.
Thx.
Joking aside WFH makes these sort of problems even worse I have considered suggesting we make all documents source controlled and use git to handle check in and out.
And trying to get people to use office 365's scs is going to be hard and if all your technical docs are in git makes sense to use on scs
next is organizations getting over the hurdle of educating people how to use version control.
Also - I think the current generation of office stores everything in XML, which can then be processed through git, svn, etc.
It was a nightmare. XML does not work well in git.[2] I even thought I could resolve some of the issues by sorting elements so they'd be in a consistent order, but none of the elements had guuids or anything to allow me to do that.
1: http://dangerousprototypes.com/blog/2010/10/14/eagle-open-xm...
2: https://blog.joepairman.com/2016/11/26/xml-in-git-mercurial-...
I have had that thought in the back of my head for a little while with my own eagle projects, thanks for making the mistake for me!