Last modified: 2011-04-22 18:35:24 UTC
It is possible to upload the same (sha1?) file over and over under the same filename. Please forbid this and handle this as nullupload in addition to an nulledit (saving an edit without changes). Thanks.
At the moment file storage is more or less tied to the versioning bits, and there's not really a way to create a "null edit" style "null upload" entry that would just reference the same file. Possible changes to the file storage system in the future may make this happen more or less 'by magic' if file refs are moved to hash-based.
Hm.. why a nullupload though ? nulledit has a purpose and exists as such, but what would a nullupload though ? I'd say we run the sha1 detection and throw a big fat warning if it's the same. Waste of space and clutters the history. People (mis|ab|re)use it all the time with the intention to change the file description (only yo find out that didn't even work).
Duplicate; if there are convincing reasons to do this, reopen the other bug. *** This bug has been marked as a duplicate of bug 15676 ***