Last modified: 2008-03-29 18:37:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13557 - Ability to delete individual diffs
Ability to delete individual diffs
Status: RESOLVED DUPLICATE of bug 3576
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-03-29 18:07 UTC by とある白い猫
Modified: 2008-03-29 18:37 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description とある白い猫 2008-03-29 18:07:31 UTC
The code for "delete" is very inefficient for the task.

In order to delete a specific diff (copyvio addition, vandalism, BLPvio) I would have to delete the entire page and restore all the diffs I do not want deleted.

In the process I waste so much time on selecting the diffs I do not want to restore particularly if the page in question underwent such an operation before. In addition the page in question appears deleted during the operation.

I should be able to selectively delete diffs without deleting the entire page. Imagine dealing with a BLP violation installed on a heavy use page like AFD or RFA or even talk pages like Jimbo's. Regular deletion and undeletion of such pages would be a serious waste of resources.
Comment 1 Raimond Spekking 2008-03-29 18:37:19 UTC

*** This bug has been marked as a duplicate of bug 3576 ***

Note You need to log in before you can comment on or make changes to this bug.