I can understand why the thread goes dead, because it's only Sublime HQ that can fix the error, hence only their request for information is sensible to spend time on.
There's a bunch of people involved in the summary previously in this thread. I've asked for more information, but here is what I do know:
1a) none on at the machine i watched it happen on, b) some are, some are not.
2) group permissions, time created (this should be retained). Happens on 3.x kernels, fedora.
3) quite simply that files can be modified, but not created. This is a no-brainer and "by design", but another reason why atomic save is bad.
5) it's an inherit weakness in the file system, but now you're in the realms of probability (which was our original point)
I think our main message is that it's senseless to spend time on fixing this feature, since it's not useful. Just nuke it.