Last modified: 2013-07-25 09:36:49 UTC
Please scrub the 2002 and 2003 edits from: http://en.wikipedia.org/wiki/Wikipedia:Sandbox I.e. these edits: http://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&offset=20040101000000&limit=100&action=history&tagfilter= I accidentally imported them there by file uploading last night. Not only that, but I also forgot to change the usernames so they're under Wikipedians' old usernames. The edits are duplicated (under the correct usernames!) at: http://en.wikipedia.org/wiki/Wikipedia:Historical_archive/Earliest_sandbox_history Another reason to remove these edits (besides the fact that they're plain ugly) is that users of automated tools sometimes use the sandbox to test speedy deletion warnings. These automated tools automatically place the speedy deletion notice on the talk page of the first contributor to the page. There is no reason to bombard the user "I am Jack's username" (either in his former or current username) with these notices.
Deleting the version by delete the whole page and restore the other revisions should be enough. I hope nobody will delete revisions physically.
Sigh.
(In reply to comment #2) > Sigh. Exactly. This is more than a little embarrassing. If only we had revision move (bug 21312) ... @db: Deletion and restoration will cause Bad Things (TM) to happen to the database and should absolutely *not* be done: http://en.wikipedia.org/wiki/Wikipedia:Village_stocks#Scientizzle_for_the_Baby_and_Bathwater_award There are actually a number of these cases on a smaller scale caused by transwiki imports (a few of mine by accident, many by someone else who didn't know any better): http://en.wikipedia.org/w/index.php?title=Special:Contributions&offset=20050201000000&limit=36&tagfilter=&contribs=user&target=Conversion+script&namespace= But these need handling on a case-by-case basis. And not all of Conversion script's edits display in Special:Cpontributions (which you'd notice if you'd click on the next button) because of bug 34873 ...
I wonder if the deleteOldRevisions.php maintenance script would be enough to fix this issue...
