Hacker News new | ask | show | jobs
by ppog 4436 days ago
...and, indeed, these XML namespaces (MS Office and data types) and the CustomDocumentProperties tag are already known to be added by SharePoint, and apparently for well-established reasons (though not ones I understand not being a SP user): http://sharepoint.stackexchange.com/questions/30626/why-is-s...
1 comments

It's absolutely inexcusable to modify .php source code files for this though!

Wonder if it would modify files in a git repository in the same way? Good luck recovering from that!

From my bad experience, Git repositories (and I would go as far as to say any source code) does not belong on SkyDrive/OneDrive. This is OneDrive, not the newfangled Hailstorm by architecture astronauts[0].

I would recommend that everyone keep working copy of their source code outside of any form of syncing. If you must, create tape archives (or 7z or something) and sync them but never your working copy.

[0] http://www.joelonsoftware.com/items/2008/05/01.html

I've kept most of my Git repos in my OneDrive for the past few years. It's worked great.

As many others have said, OneDrive For Business is really more of a SharePoint + Groove document sharing / collaboration thing for businesses documents (as the name kind of implies). While it does similar things from a generic corporate user point of view, the mechanics are pretty different. OneDrive For Business works well for the same kinds of use cases that SharePoint does (mostly documents), but I wouldn't put source code in there.

Good to know one shouldn't treat the OneDrive as a... Drive.
OneDrive is a drive as you would expect. OneDrive for Business is really SharePoint. Terrible branding.
git reset? I can't imagine any way in which it would destructively modify the files under objects/
Why not? The article claimed it modified a .php file. So I'm curious to know if it would modify the equivalent file under .git/objects?
Because the equivalent file is either compressed with a custom header or in a totally-incomprehensible-to-it binary pack.

Let me put it this way: I would be scared to store an svn checkout because of how svn stores metadata copies. I wouldn't worry about a git checkout.