408:
redirect to the source. When a redirect is blocking a full MergeHistory merge, the redirect and any older edits will need to be either deleted or merged to another redirect. Deletion and restoration of pages with lengthy edit histories is very time- and resource-intensive, and administrators are not allowed to delete pages with more than 5000 edits in their history. An easier option in these cases may be to history-merge the redirect and any earlier history to another redirect that was created later. See
763:
144:
1383:. As long as these two revisions are located on different titles, this isn't a problem. However, if the two edits are inadvertently histmerged to the same page, and then temporarily deleted, it is impossible to restore one of these edits without restoring both of them, because they share the identical timestamp which identifies which edit to restore. Thus care should be taken not to move or histmerge a page-move generated
562:
594:(That is, the move tool was not available or not used to simultaneously transfer the Wiki text and the history of edits to the new title.) And suppose this replacement (new-title) article develops further and reflects the new history of these further edits. Our goal is to graft the (old) edit history from
330:
The ideal situation for a history merge is when an editor copies and pastes all content from one page to a brand new page, and then the old page does not receive any more edits. In other words, where the first page's history stops, the second page's history begins, and there are no overlapping diffs.
192:
may move a new article to the Draft space and the original editor will simply recreate it in the
Article space. In both of these situations, if the original editor is the only one that has contributed content to the pages, a history merge is not necessary because there are no attribution issues (only
975:
Also, if page A is to be history-merged into page B, before the process, make sure that there are no deleted edits in page B, as then deleting B will shuffle the deleted and non-deleted edits attached to the page together. The deleted history should first be rescued from under B by some process such
957:
The MediaWiki software does not allow page history to be publicly archived at a page title that does not host a live page or redirect. Therefore, if two pages with parallel histories are merged but it is undesirable to keep a redirect from the deprecated page title to the destination page title, the
407:
It automatically detects the latest version of the source page which is older than the oldest version of the target page, and won't allow the user to move later revisions. This feature is good if the source page eventually became something else, but can be bad if the target page had started out as a
953:
An appropriate procedure for such a case is to forego the history merge, and instead handle the situation much like a normal merge; put a note pointing to the other version of the page on the article's talk page. If it is inappropriate to leave the second copy in the main article space, you can
895:
However, the examples just described only work well if the two pieces of the history of one 'article' are disjoint; i.e. one ends before the other begins. These procedures are inadequate if this condition does not apply, e.g., if the copy of the article at the old title has been edited
1017:(overwriting the old) and continue editing. If this is not caught immediately it is very easy for the new topic to build up a substantial edit history of its own. Admins can use the following steps to fix this problem and maintain separate histories for the separate topics:
1109:, and both pages will display the request to perform a history-merge. An admin should not try to perform a history-merge on page Y, but only on page X. This is most likely to happen if page X is a template, but it may happen to any page that is transcluded. To avoid this,
839:, select the next-most-recent version, click on it, and when it appears, click on "Edit this page", ignore the "WARNING: You are editing an out-of-date revision" message, type something suitable (e.g., "restoring most recent version after merging histories") in the
151:
A history merge is required for attribution purposes, as attribution is lost during a cut/paste page move where there are multiple editors at the old page. In the image shown, it appears as if the user
Thegreatrebellion had created the entirety of the added text at
338:. If the two pages have separate origins and simultaneous separate parallel histories before they were text-merged, they should not be history-merged, as that would shuffle the parallel editing histories together in one list and make a mess. There is an example in
950:(and/or vice-versa). Inspecting this merged history without means of distinguishing between the two overlapping progressions (since nothing in this history indicates which version belongs to which sequence) invites severe confusion.
976:
as this: Move B to some other name, say B_zxcvbnm (without making a redirect). Undelete B. Move B to some other name, say B/old_version . If necessary, re-delete B/old_version . Move B_zxcvbnm back to B (without making a redirect).
1693:
1062:
In most cases, you will be moving all non-redirect versions of one page into the history of another and leaving a redirect. Please keep the following situations in mind when deciding what to do with the redirect:
187:
New editors are often unaware of the ability to move pages (or are unable because of new-account restrictions), and will thus copy/paste a draft they have been working on into the article space. Similarly, a
771:
To select more than one revision for undeletion, click on the tick box of the first revision to be undeleted, then shift-click on the last revision to be undeleted. Every intermediate revision will then be
1143:
If a history merge should not have been performed, then it may be undone. Note, however, that it can be quite tedious, especially if the article has a very long history. The following procedure is listed:
1270:
When a page is moved, two edits are made, with consecutively numbered revision IDs and identical timestamps & edit summaries. In edit histories, the timestamps are usually shown to the minute (
1398:, but in practice this is a particularly inelegant and tedious method for anything other than what it was designed for (i.e. history-merging). Here's a sketch of how it would need to be done:
621:
1723:
1673:
531:
Instead of finding redirects, you can make a temporary page (for example, in draftspace), merge the blocking redirect history there, and then delete the temporary page when you're done.
755:
page). That causes the article now at NewTitle to have part of its history there, and part at OldTitle, but the history at OldTitle also contains the history of NewMeaning. Use of the
479:
Deletion and restoration operations often time out with errors on pages with long edit histories. Simply try the delete or restore again; it virtually always succeeds on the second try
1678:
1668:
265:
If there are no changes since the copied-from revision in either the original page or the pasted-to page, consider tagging the pasted page for temporary deletion using
1635:
476:
Restore all but the previously deleted edits and the oldest (redirect) revision(s) – these would have been deleted by a regular move when it "moved over the redirect"
1688:
1581:
958:
old page history needs to move. This is sometimes done by moving the page history to a subpage of the talk page of the destination page. An example can be found at
1791:
1703:
120:
of an article or talk page can be split among two or more different pages. This is highly undesirable, because we need to keep the history with the content for
705:
had too many revisions to be deleted or deleting it may cause other disruption. The following procedure can be used to merge page histories in this situation:
1713:
1683:
1663:
28:
506:
Find an appropriate redirect, whose oldest revision (creation date) is newer than the most recent revision of the redirect history that needs to be cleared
524:
Now MergeHistory can do the merge; this technique avoids making a new edit that needs to be reverted, which happens when the source is moved to the target
482:
Now MergeHistory can do the merge; this technique avoids making a new edit that needs to be reverted, which happens when the source is moved to the target
1708:
1658:
1718:
979:
Likewise, if a page must be deleted and then partly undeleted for a history-split, first check in case it is sitting over a deleted parallel history.
99:
1106:
684:(Shift+Control+R in Mozilla or Opera, Ctrl+F5 in Internet Explorer, and Ctrl+R in Firefox) to see an up-to-date history reflecting the undeletion.
365:
226:
125:
287:
46:
751:
Sometimes, after a cut-and-paste move is performed, the article at the old title is then edited for some other purpose (e.g., turning it into a
861:
restores the more recent history of that article; no additional steps are needed, as the most recent version should now be the current version.
1575:
32:
1075:)? As with regular page moves, consider waiting a few days before deleting the leftover redirect even if it is eligible for speedy deletion.
959:
637:
Clicking on "Restore". (Now the new title's history has both the old and new versions, including an extra copy of the most recent version of
1245:
1105:
If page X is transcluded in page Y, and page X is marked to be the recipient in a history-merge, then page X and page Y will both appear in
248:-related templates, edits which were reverted, etc.), place {{History merge|NAME OF PAGE THE ARTICLE WAS CUT FROM|reason=|details=}} at the
1628:
576:(old title) was the only article on that subject, and that the article developed in the course of a number of edits, until a decision that
1806:
463:
Move the page with the oldest (redirect) revision(s) back to mainspace, then delete it (adding to the already existing deleted revisions)
1801:
1644:
514:
717:
with a move summary like "history merge, will be back at correct title soon". Answer yes when asked to delete the
Alabama/History page.
580:(new title) was a better style of name for the article. Suppose further that for whatever reason, the contents of the old article were
1005:
Over time, articles may change from one underlying topic to a completely separate topic. Normally this should be accomplished through
415:
The user can, however, tell it to only move earlier revisions than that – it is possible to select the latest revision it should move.
843:, and hit "Save page". That article is now restored to its condition prior to this procedure, and now also has its complete history.
351:
510:
889:
1621:
364:
template and place it on the source and/or destination's talk page, in order to meet the copyright attribution requirements of
347:
339:
1559:
1081:
Is it likely the most recent editors of the moved revisions are watchlisting the page? Consider notifying them of the change.
756:
427:
If the user moves all non-deleted revisions of the source, a hard redirect is automatically created. This can't be overridden.
240:
In cases where additional edits were made to the original version after the copy-and-paste and which the additional edits can
95:
954:
archive the duplicate page to Talk: space (i.e. by moving it to some suitable title, such as Talk:RandomArticle/OldVersion).
762:
460:
Restore the oldest (redirect) revision(s) – these would have been deleted by a regular move when it "moved over the redirect"
1769:
1763:
1091:
A redirect from the "main" user page or "main" user talk page to somewhere other than another page in that user's userspace.
681:
561:
1227:
1219:
157:
1370:
1084:
Is the leftover redirect in User: or User_talk: space? If you do delete it, notify the affected user unless there is a
1796:
1757:
1751:
276:
110:
109:
is necessary, or when the move function fails (e.g., because the target has history) and people don't know to use the
1745:
1739:
1094:
A redirect to another user's pages or non-user space in a way that may cause confusion or is otherwise inappropriate.
1028:
1010:
752:
132:
1214:
is now a redirect to itself or the other article, then revert or change the redirect target, as deemed appropriate.
1562:
and is marked as unreviewed; it is also a good idea to check for this and manually review the page if necessary (
966:
836:
828:
821:
814:
810:
781:
1334:
0 — an edit is made on the target documenting the move in the edit summary, with no difference in page content
840:
117:
170:
The editor who blanked and/or redirected the page used an edit summary such as "move to <new page name: -->
1546:
as soon as they happen. After performing a history merge, it is a good idea to check your
Wikidata contribs (
602:(article with new title) where those partial histories can complement each other. The process is as follows:
343:
196:
If trivial edits are made by other editors, such as maintenance tags or categorisation, and these edits are
163:
While this is not an exhaustive list, any pages meeting the below criteria may be eligible for a histmerge:
1379:
Live edits are uniquely identified by their revision ID numbers, but deleted edits are referenced by their
256:
233:
212:
1597:
1586:
1078:
Are all incoming links to the leftover redirect fixed? If not, don't delete the redirect until they are.
121:
493:
269:
105:
Cut-and-paste moves still occur today because of unfamiliarity with the move function, unawareness that
1543:
1126:
988:
871:
382:
299:
156:, when the reality is that there were contributions from over 200 editors at the previous page name of
52:
39:
1547:
1455:
1432:
1395:
1359:
1348:
1313:
1088:
not to. Consider leaving the redirect unless doing so would cause problems, such as in the case of:
400:
280:
1591:
1014:
457:
Move the page to draft: namespace before deleting it, with the rationale: "history-merging process".
334:
Users sometimes send in an ill-advised history-merge request after the two pages involved have been
1072:
1068:
106:
1607:
732:
710:
702:
674:
667:
659:
651:
647:
625:
615:
611:
599:
577:
1443:, merge those edits to the temporary userpage. If the first undeleted edits should be merged to
245:
1278:
date format preference is set; however, in the database they are recorded to the second, e.g.:
143:
858:
847:
832:
806:
799:
792:
785:
777:
431:
1006:
919:
later to be reverted to an article on the same topic, with a sequence of edits there as well.
835:(it's a copy of that version, created by the page-move function). So, go into the history of
252:
as described above. Fill in the two parameters as needed for this particular situation (see
788:
was then turned into a disambiguation page. This was repaired with the following procedure:
1085:
1024:
Restore previous revisions up to (but not including) the point where the topic was changed.
189:
739:
728:
721:
714:
663:
655:
638:
607:
595:
573:
358:
569:
The following procedure merges the page histories in the case of a hypothetical example:
1533:
1391:
s should stay on the page on which they were created, either as live or deleted edits.
1261:
687:
286:
In more complex cases (explained below), please leave a description of the problem at
1785:
900:
the pasting of its contents into the new title. For example, it is not uncommon for:
91:
1484:
Delete the temporary empty userpage, and undelete all revisions to be moved back to
1034:
If there is already an article under the new name and you wish to histmerge into it:
1602:
1428:
Create a temporary empty userpage to hold the revisions while performing the split.
618:
to allow the move. (Now the old versions are the whole of the new title's history.)
335:
447:
Check for deleted history at the target, and take note of all deleted edits there
17:
1613:
153:
846:
Step 3 above (the move) will have left a history containing just a redirect at
200:
transferred over by the primary content author, a history merge is not needed.
174:
The new page was originally a redirect and was overwritten by the "new" article
1013:
pages. However, if a user is unfamiliar with those processes they may simply
403:, to perform history merges. It differs from the manual methods, as follows:
232:
Consider notifying the user of the issue on their talk page, perhaps using {{
1421:, we notice that extra edits with the same timestamp that need to remain on
283:
or a similar tool should be used to verify that no changes have been made.
1528:
1256:
934:
using the method described above, the result will sequence the versions of
90:
In the early days of
Knowledge (XXG), renamings took place manually, using
473:
Delete the target page with the rationale "setting up for a history merge"
1275:
135:
can fix this by merging page histories, using the procedure given below.
1558:
Similarly when a page is deleted and then undeleted, it is added to the
1507:
and revert the latest move edit back to the previous latest revision on
1477:(the revisions should not be mixed anymore after step 5), then undelete
923:
In this case, the time periods of the two series of edits will overlap.
167:
There are several editors in the page history at the original location
1047:
Restore new revisions of new topic (still at original article name)
418:
It doesn't mix deleted and non-deleted versions of the target page.
1218:
An example of a successful history merge and undo is available at
142:
1039:
a) select the "delete the existing article" option, while moving;
946:
will be interleaved between versions in the page history of page
824:
restores the rest of the versions of that article to its history.
1027:
Move the restored versions (old topic) to a new name (see also
1617:
817:
must be deleted, although this can be done as part of the move.
509:
Merge the blocking redirect history to that redirect. Example:
798:
Selective undelete is used to undelete only those versions of
548:
by spending quite silly amounts of time. To undo a merge, see
662:
page will now be showing whatever the most recent version of
430:
The logs for this action aren't in the move log - they're in
38:"WP:CUT" redirects here. For the guideline on shortcuts, see
1067:
Is the resulting redirect eligible for speedy deletion (see
972:
template for tagging parallel versions found on talk pages.
761:
560:
518:
502:
942:
strictly by time, with the result that various versions of
813:, using the normal page-move function. For this to happen,
513:. The April and July 2005 revisions were merged here from
466:
Restore the remaining history and move it back to mainspace
409:
1550:) and restore pages to their previous state if necessary.
590:
pasted into a newly created article bearing the new title.
1514:
You should now end up with the correct edits merged into
1488:(so to exclude the revision of you creating the userpage)
1053:
Establish a disambiguation page for the different topics
666:
was). The last step is to revert to the last version of
1563:
1353:
1325:
1318:
1134:
996:
879:
831:
is now the most recent version of the old history from
501:
497:
390:
321:
314:
307:
81:
74:
67:
60:
1367: -8,264 — the source page's text was replaced with
960:
Talk:Compilation of Final
Fantasy VII#Old page history
654:" (assuming a redirect was the most recent version of
614:, using the move tool. The admin approves deletion of
552:. Do not do this if you're not sure what you're doing.
225:
was done. The page will appear in the hidden category
1394:
These can, however, theoretically be separated using
634:
Linking via "View or restore ... deleted edits?", and
1542:
Page moves and deletions are generally reflected on
587:
replaced in it with a redirect to the new title, and
489:
To clear a blocking redirect by history-merging it:
1732:
1651:
1582:
Knowledge (XXG):Viewing and restoring deleted pages
827:However, the most recent version in the history of
697:
Merging page histories of pages with many revisions
421:
It retains any protection the target page may have.
204:
Instructions for tagging a page for history merging
451:
598:(article with old title) onto the new history in
424:It doesn't create a new revision of the old page.
147:An example of an inappropriate cut/paste pagemove
549:
805:The versions of "Japan Self-Defense Forces" at
738:If needed, undelete the remaining revisions at
346:. There is an example with 5 incoming pages in
29:Knowledge (XXG):Copying text from other sources
1495:if there are remaining undeleted revisions on
802:which belonged to "Japan Self-Defense Forces".
759:function allows these to be repaired as well.
492:Find other redirects to the target page using
366:Knowledge (XXG):Copying within Knowledge (XXG)
126:Knowledge (XXG):Copying within Knowledge (XXG)
27:For information on copy and pasting text, see
1629:
444:To clear a blocking redirect by deleting it:
100:enabled for non-administrators in August 2002
8:
193:one editor has written all of the content).
888:"WP:PV" redirects here. For pageviews, see
784:with a cut-and-paste move, and the article
354:. The best thing to do would be to use the
1636:
1622:
1614:
1021:Delete the article (original article name)
926:If someone then page-history merges pages
288:Knowledge (XXG):Requests for history merge
47:Knowledge (XXG):Requests for history merge
1576:Knowledge (XXG):WikiProject History Merge
1042:b) restore deleted revisions of new name.
33:Knowledge (XXG):WikiProject History Merge
1280:
1246:Knowledge (XXG):History merging/Old bugs
1050:Revert to latest good versions as needed
496:, while hiding links and transclusions:
410:§ Clearing away merge-blocking redirects
215:|NAME OF PAGE THE ARTICLE WAS CUT FROM}}
1724:Viewing deleted pages and contributions
1499:. Move the temporary empty userpage to
1107:Category:Candidates for history merging
399:Administrators can use a special page,
116:When a cut-and-paste move is done, the
1199:Undelete the rest of the revisions of
1177:Selectively undelete the revisions of
439:Clearing away merge-blocking redirects
1792:Knowledge (XXG) Administrators' guide
1402:Suppose we want to move revisions of
1387:edit off of the page it was made on.
1299:difference in bytes and page content
908:to be cut and pasted into (new) page
7:
1058:How to handle the left-over redirect
352:Knowledge (XXG) talk:WikiProject Emo
1610:(requesting a simple history split)
890:Knowledge (XXG):Pageview statistics
650:will only show the text "#redirect
515:Yasser Arafat International Airport
377:Using the MergeHistory special page
279:), and then do a proper page move.
1503:. Undelete the other revisions on
1435:, if the first undeleted edits on
1417:After undeleting the revisions of
1101:History-merging a transcluded page
25:
1694:Granting and revoking user rights
511:Special:PageHistory/Gaza Airport
113:forum to start a move request.
1807:Knowledge (XXG) history merges
1461:If the remaining revisions on
1015:change the topic of an article
227:Candidates for history merging
1:
1659:Advice for new administrators
1251:Revisions with same timestamp
1228:User:King of Hearts/Sandbox/7
1220:User:King of Hearts/Sandbox/6
1152:has been history merged into
690:to the last pre-move version.
544:: this procedure may only be
158:Syed Saddiq Syed Abdul Rahman
1447:, then merge those edits to
1181:that made up the history of
780:; the original was moved to
724:containing the page history.
641:, created by the move tool.)
1578:(how to reduce the backlog)
1465:still need to be merged to
1163:s former history back into
1121:How to undo a history merge
673:Clicking "Page history" on
372:Repair process (for admins)
139:When to request a histmerge
31:. For the WikiProject, see
1823:
1802:Administrator instructions
1719:Tools, scripts and gadgets
1526:
1473:, move those revisions to
1254:
1243:
1124:
986:
887:
869:
720:Undelete the revisions of
452:co-mingled revisions issue
380:
297:
244:be safely discarded (e.g.
50:
44:
37:
26:
1598:Knowledge (XXG):Splitting
1587:Knowledge (XXG):Integrate
1425:have also been undeleted.
1371:Élie Decazes, Duc Decazes
1354:Élie Decazes, Duc Decazes
1326:Élie Decazes, Duc Decazes
1319:Élie Decazes, Duc Decazes
1185:before the history merge.
904:an article at (old) page
837:Japan Self-Defense Forces
829:Japan Self-Defense Forces
822:Japan Self-Defense Forces
815:Japan Self-Defense Forces
811:Japan Self-Defense Forces
782:Japan Self-Defense Forces
670:from before the move, by
631:Viewing the Page history,
584:cut from the old article,
1770:Revision deletion policy
766:Steps for a complex case
40:Knowledge (XXG):Shortcut
1592:Knowledge (XXG):Merging
1458:cannot be used anymore.
1272:17:47, 21 January 2008
776:An example of this was
565:Steps for a simple case
344:Clemson Tigers football
131:In some circumstances,
1797:Knowledge (XXG) how-to
853:Undeletion of all the
850:. Delete the redirect.
767:
701:Suppose that the page
566:
183:to request a histmerge
148:
1674:Dealing with disputes
1645:Administrators' guide
765:
564:
494:Special:WhatLinksHere
322:WP:Parallel histories
277:WP:Speedy deletion#G6
146:
1740:Administrator policy
1456:Special:MergeHistory
1454:Repeat step 4 until
1433:Special:MergeHistory
1396:Special:MergeHistory
1113:should be placed in
450:WARNING: Beware the
401:Special:MergeHistory
281:Special:ComparePages
234:subst:uw-c&pmove
1073:WP:SPEEDY#Redirects
747:A more complex case
498:What redirects here
1608:Template:Histsplit
1439:need to remain on
1410:. We first delete
1115:<noinclude: -->
866:A troublesome case
768:
757:selective deletion
733:History of Alabama
711:History of Alabama
703:History of Alabama
675:History of Alabama
668:History of Alabama
660:History of Alabama
652:History of Alabama
648:History of Alabama
626:History of Alabama
616:History of Alabama
612:History of Alabama
600:History of Alabama
578:History of Alabama
567:
149:
18:Knowledge (XXG):PV
1779:
1778:
1764:Protection policy
1679:Dealing with spam
1669:Cleaning backlogs
1377:
1376:
1360:Élie, duc Decazes
1349:Élie, duc Decazes
1314:Élie, duc Decazes
1238:Bugs and problems
1111:{{history merge}}
1069:WP:SPEEDY#General
983:History splitting
859:Military of Japan
848:Military of Japan
833:Military of Japan
807:Military of Japan
800:Military of Japan
793:Military of Japan
786:Military of Japan
778:Military of Japan
294:Parallel versions
262:for an example).
190:New Page Reviewer
16:(Redirected from
1814:
1638:
1631:
1624:
1615:
1548:convenience link
1538:
1536:
1390:
1386:
1373:
1356:
1328:
1321:
1281:
1273:
1266:
1264:
1137:
1117:tags on page X.
1116:
1112:
999:
971:
967:Parallel version
965:
882:
393:
363:
357:
324:
317:
310:
274:
268:
261:
255:
216:
84:
77:
70:
63:
21:
1822:
1821:
1817:
1816:
1815:
1813:
1812:
1811:
1782:
1781:
1780:
1775:
1758:Deletion policy
1752:Blocking policy
1728:
1699:History merging
1647:
1642:
1572:
1556:
1540:
1534:
1532:
1525:
1388:
1384:
1368:
1352:
1324:
1317:
1271:
1268:
1262:
1260:
1253:
1248:
1240:
1159:We want to get
1141:
1140:
1133:
1129:
1123:
1114:
1110:
1103:
1060:
1003:
1002:
995:
991:
985:
969:
963:
893:
886:
885:
878:
874:
868:
749:
740:Alabama/History
729:Alabama/History
722:Alabama/History
715:Alabama/History
699:
664:Alabama/History
656:Alabama/History
646:At this stage,
639:Alabama/History
608:Alabama/History
596:Alabama/History
574:Alabama/History
559:
538:
441:
397:
396:
391:WP:MERGEHISTORY
389:
385:
379:
374:
361:
355:
328:
327:
320:
313:
306:
302:
296:
272:
266:
259:
253:
210:
206:
185:
141:
111:Requested moves
88:
87:
80:
73:
66:
59:
55:
49:
43:
36:
23:
22:
15:
12:
11:
5:
1820:
1818:
1810:
1809:
1804:
1799:
1794:
1784:
1783:
1777:
1776:
1774:
1773:
1767:
1761:
1755:
1749:
1746:Banning policy
1743:
1736:
1734:
1730:
1729:
1727:
1726:
1721:
1716:
1711:
1706:
1701:
1696:
1691:
1686:
1681:
1676:
1671:
1666:
1661:
1655:
1653:
1649:
1648:
1643:
1641:
1640:
1633:
1626:
1618:
1612:
1611:
1605:
1600:
1595:
1594:(text merging)
1589:
1584:
1579:
1571:
1568:
1560:new pages feed
1555:
1552:
1539:
1531:
1524:
1521:
1520:
1519:
1512:
1489:
1482:
1459:
1452:
1429:
1426:
1415:
1375:
1374:
1365:
1362:
1357:
1345:
1343:
1340:
1336:
1335:
1332:
1329:
1322:
1310:
1308:
1305:
1301:
1300:
1297:
1294:
1291:
1288:
1285:
1274:), unless the
1267:
1259:
1252:
1249:
1239:
1236:
1216:
1215:
1204:
1197:
1186:
1175:
1168:
1157:
1139:
1138:
1130:
1125:
1122:
1119:
1102:
1099:
1098:
1097:
1096:
1095:
1092:
1082:
1079:
1076:
1059:
1056:
1055:
1054:
1051:
1048:
1045:
1044:
1043:
1040:
1036:
1035:
1029:disambiguation
1025:
1022:
1011:disambiguation
1001:
1000:
992:
987:
984:
981:
921:
920:
913:
884:
883:
875:
870:
867:
864:
863:
862:
851:
844:
825:
820:Undeletion of
818:
803:
796:
753:disambiguation
748:
745:
744:
743:
736:
725:
718:
698:
695:
694:
693:
692:
691:
685:
678:
644:
643:
642:
635:
632:
619:
592:
591:
588:
585:
558:
555:
537:
536:Manual process
534:
533:
532:
529:
528:
527:
526:
525:
507:
504:
487:
486:
485:
484:
483:
480:
474:
471:
470:
469:
468:
467:
464:
461:
458:
454:. WORKAROUND:
440:
437:
436:
435:
432:a separate log
428:
425:
422:
419:
416:
413:
395:
394:
386:
381:
378:
375:
373:
370:
326:
325:
318:
311:
303:
298:
295:
292:
238:
237:
230:
205:
202:
184:
177:
176:
175:
172:
168:
140:
137:
133:administrators
124:reasons. (See
86:
85:
78:
71:
64:
56:
51:
24:
14:
13:
10:
9:
6:
4:
3:
2:
1819:
1808:
1805:
1803:
1800:
1798:
1795:
1793:
1790:
1789:
1787:
1771:
1768:
1765:
1762:
1759:
1756:
1753:
1750:
1747:
1744:
1741:
1738:
1737:
1735:
1731:
1725:
1722:
1720:
1717:
1715:
1712:
1710:
1707:
1705:
1702:
1700:
1697:
1695:
1692:
1690:
1687:
1685:
1682:
1680:
1677:
1675:
1672:
1670:
1667:
1665:
1662:
1660:
1657:
1656:
1654:
1650:
1646:
1639:
1634:
1632:
1627:
1625:
1620:
1619:
1616:
1609:
1606:
1604:
1601:
1599:
1596:
1593:
1590:
1588:
1585:
1583:
1580:
1577:
1574:
1573:
1569:
1567:
1565:
1561:
1554:Page curation
1553:
1551:
1549:
1545:
1537:
1530:
1522:
1517:
1513:
1510:
1506:
1502:
1498:
1494:
1490:
1487:
1483:
1480:
1476:
1472:
1468:
1464:
1460:
1457:
1453:
1450:
1446:
1442:
1438:
1434:
1430:
1427:
1424:
1420:
1416:
1413:
1409:
1405:
1401:
1400:
1399:
1397:
1392:
1382:
1372:
1366:
1363:
1361:
1358:
1355:
1350:
1346:
1341:
1338:
1337:
1333:
1330:
1327:
1323:
1320:
1315:
1311:
1306:
1303:
1302:
1298:
1295:
1292:
1290:edit summary
1289:
1286:
1283:
1282:
1279:
1277:
1265:
1258:
1250:
1247:
1242:
1237:
1235:
1233:
1229:
1226:article) and
1225:
1221:
1213:
1209:
1205:
1202:
1198:
1195:
1191:
1187:
1184:
1180:
1176:
1173:
1169:
1166:
1162:
1158:
1155:
1151:
1147:
1146:
1145:
1136:
1132:
1131:
1128:
1120:
1118:
1108:
1100:
1093:
1090:
1089:
1087:
1083:
1080:
1077:
1074:
1070:
1066:
1065:
1064:
1057:
1052:
1049:
1046:
1041:
1038:
1037:
1033:
1032:
1030:
1026:
1023:
1020:
1019:
1018:
1016:
1012:
1008:
998:
994:
993:
990:
982:
980:
977:
973:
968:
961:
955:
951:
949:
945:
941:
937:
933:
929:
924:
918:
914:
911:
907:
903:
902:
901:
899:
891:
881:
877:
876:
873:
865:
860:
856:
852:
849:
845:
842:
838:
834:
830:
826:
823:
819:
816:
812:
809:are moved to
808:
804:
801:
797:
794:
791:
790:
789:
787:
783:
779:
774:
773:
764:
760:
758:
754:
746:
741:
737:
734:
730:
726:
723:
719:
716:
712:
708:
707:
706:
704:
696:
689:
686:
683:
679:
676:
672:
671:
669:
665:
661:
657:
653:
649:
645:
640:
636:
633:
630:
629:
627:
623:
620:
617:
613:
609:
605:
604:
603:
601:
597:
589:
586:
583:
582:
581:
579:
575:
570:
563:
556:
554:
553:
551:
547:
543:
535:
530:
523:
522:
520:
516:
512:
508:
505:
503:
499:
495:
491:
490:
488:
481:
478:
477:
475:
472:
465:
462:
459:
456:
455:
453:
449:
448:
446:
445:
443:
442:
438:
433:
429:
426:
423:
420:
417:
414:
411:
406:
405:
404:
402:
392:
388:
387:
384:
376:
371:
369:
367:
360:
353:
349:
345:
341:
337:
332:
323:
319:
316:
312:
309:
305:
304:
301:
293:
291:
289:
284:
282:
278:
271:
263:
258:
257:history merge
251:
247:
243:
235:
231:
228:
224:
220:
214:
213:History merge
208:
207:
203:
201:
199:
194:
191:
182:
178:
173:
169:
166:
165:
164:
161:
159:
155:
145:
138:
136:
134:
129:
127:
123:
119:
114:
112:
108:
103:
101:
98:function was
97:
94:, before the
93:
92:cut and paste
83:
79:
76:
72:
69:
65:
62:
58:
57:
54:
48:
41:
34:
30:
19:
1766:(WP:PROTECT)
1709:Reading list
1698:
1689:Edit filters
1603:Help:Merging
1557:
1541:
1515:
1508:
1504:
1500:
1496:
1492:
1485:
1478:
1474:
1470:
1466:
1462:
1448:
1444:
1440:
1436:
1422:
1418:
1411:
1407:
1403:
1393:
1380:
1378:
1269:
1241:
1231:
1223:
1217:
1211:
1207:
1200:
1193:
1189:
1182:
1178:
1171:
1164:
1160:
1153:
1149:
1142:
1104:
1061:
1004:
997:WP:HISTSPLIT
978:
974:
956:
952:
947:
943:
939:
935:
931:
927:
925:
922:
916:
909:
905:
897:
894:
857:versions of
854:
841:edit summary
775:
770:
769:
750:
700:
628:article, by
593:
571:
568:
557:An easy case
545:
541:
540:
539:
398:
333:
329:
285:
270:db-copypaste
264:
250:new location
249:
241:
239:
222:
221:, where the
219:new location
218:
197:
195:
186:
180:
162:
150:
130:
118:page history
115:
104:
89:
75:WP:HISTMERGE
1772:(WP:REVDEL)
1564:example log
1535:Task T75908
1529:Phabricator
1527:Tracked in
1263:Task T30819
1257:Phabricator
1255:Tracked in
1086:good reason
795:is deleted.
682:hard reload
336:text-merged
154:Syed Saddiq
107:attribution
82:WP:CUTPASTE
1786:Categories
1754:(WP:BLOCK)
1742:(WP:ADMIN)
1704:Protecting
1381:timestamps
1369:#REDIRECT
1342:2008-01-21
1339:185912121
1307:2008-01-21
1304:185912120
1287:timestamp
1244:See also:
1234:article).
962:. Use the
45:See also:
1469:, delete
1389:#REDIRECT
1385:#REDIRECT
1344:17:47:32
1309:17:47:32
1135:WP:HMUNDO
772:selected.
688:Reverting
500:Example:
348:this edit
340:this edit
300:Shortcuts
122:copyright
96:move page
53:Shortcuts
1760:(WP:DEL)
1748:(WP:BAN)
1733:Policies
1714:Rollback
1684:Deleting
1664:Blocking
1652:Articles
1570:See also
1544:Wikidata
1523:Wikidata
1276:ISO 8601
1148:Suppose
1127:Shortcut
989:Shortcut
872:Shortcut
731:back to
622:Undelete
572:Suppose
383:Shortcut
350:of page
342:of page
315:WP:PHIST
246:WP:WPAFC
1491:Delete
1210:and/or
1170:Delete
680:Make a
542:Warning
308:WP:PVER
223:pasting
217:at the
1431:Using
1347:moved
1331:8,304
1312:moved
1296:bytes
1293:title
1284:revid
658:, the
546:undone
359:Copied
209:Place
68:WP:CUT
1406:into
1230:(the
1222:(the
1188:Move
1007:moves
915:page
912:, and
898:after
880:WP:PV
855:other
727:Move
709:Move
606:Move
550:below
275:(see
179:When
61:WP:HM
1071:and
1009:and
938:and
930:and
624:the
1566:).
1364:40
1351:to
1316:to
1206:If
1192:to
713:to
610:to
519:log
242:all
236:}}.
198:not
181:not
128:.)
1788::
1161:A'
1031:)
970:}}
964:{{
521:)
368:.
362:}}
356:{{
290:.
273:}}
267:{{
260:}}
254:{{
211:{{
160:.
102:.
1637:e
1630:t
1623:v
1518:.
1516:B
1511:.
1509:A
1505:A
1501:A
1497:A
1493:A
1486:A
1481:.
1479:B
1475:B
1471:B
1467:B
1463:A
1451:.
1449:B
1445:B
1441:A
1437:A
1423:A
1419:A
1414:.
1412:A
1408:B
1404:A
1232:B
1224:A
1212:B
1208:A
1203:.
1201:B
1196:.
1194:A
1190:B
1183:A
1179:B
1174:.
1172:B
1167:.
1165:A
1156:.
1154:B
1150:A
948:B
944:A
940:B
936:A
932:B
928:A
917:A
910:B
906:A
892:.
742:.
735:.
677:.
517:(
434:.
412:.
229:.
171:"
42:.
35:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
