Wikipedia talk:Requests for history merge#Purpose of this page

{{shortcut|WT:SPLICE|WT:REPAIR}}

{{archives}}

{{User:MiszaBot/config

| algo = old(180d)

| archive = Wikipedia talk:Requests for history merge/Archive %(counter)d

| counter = 1

| maxarchivesize = 120K

| archiveheader = {{Talk archive navigation}}

| minthreadstoarchive = 2

| minthreadsleft = 4

}}

Best practice for reversing the direction of a merge?

I'm not sure where best to ask, but I've looked in a few places and the thread above about Étienne de Perier is the most relevant discussion I've found.

The article on the dragonfly genus Hypopetalia and it's only species, Hypopetalia pestilens, and were created on the same day in 2007. Hypopetalia was merged into Hypopetalia pestilens in 2011. Hypopetalia pestilens has 38 revisions, 26 of them after the merge; Hypopetalia has 15 revisions, 5 of them after the merge.

Per WP:MONOTYPICFAUNA, when a genus has a single species both genus and species should be covered in a single article with the genus name (typically) as the title.

What is the best practice to reverse the direction of the merge? A standard move would destroy the history of one of the pages, and round-robin would swap the histories in a confusing way. I'm thinking I should just do what is essentially a cut-and-paste move (with some modifications in phrasing) and history merge (or partial history merge) would just result in making it more confusing to understand the histories of each page. Should I cut-and-paste and add {{tl|copied}} to the talk page? Is there a better solution? Plantdrew (talk) 02:17, 13 November 2023 (UTC)

:No, I think a round-robin is called for here. Izno (talk) 03:06, 13 November 2023 (UTC)

::Agree with a swap; as long as the move from Hypopetalia pestilens to Hypopetalia clearly states why the page is being moved, it will explain any complexities in the history. Primefac (talk) 08:00, 13 November 2023 (UTC)

Same timestamp splits now possible

As of the next MediaWiki version it will be possible to use Special:MergeHistory (but not selective undeletion) to split two revisions with the same timestamp. Posting here to let any other history mergers know. * Pppery * it has begun... 00:38, 6 January 2024 (UTC)

:Spiffy. Primefac (talk) 15:05, 6 January 2024 (UTC)

Backlog

With Anthony Appleyard sadly gone, there seems to be a lack of admins checking :Category:Candidates for history merging, with pages tagged since 1 September still unaddressed. Should the threshold be reduced for the backlog template on the category page? --Paul_012 (talk) 07:08, 13 September 2024 (UTC)

:It's 13 pages, not the worst I've seen. Been a little busy with work recently but I'll shuffle this back into my routine. Primefac (talk) 10:24, 13 September 2024 (UTC)

:I don't think changing the backlog threshold would help. Unknowing admins stumbling into history merging can tend toward... hard to fix. Izno (talk) 16:36, 13 September 2024 (UTC)

::I left one for you Primefac. Izno (talk) 17:29, 13 September 2024 (UTC)

:::Hah! Thanks. Primefac (talk) 11:54, 14 September 2024 (UTC)

History merges performed using the Mergehistory special page are now logged at both the source and destination, not just the source

The subject line basically says it all. this is due to this RFC and the patch submitted for T118132. Now I don't have to make edits like this one where history merges would otherwise be difficult to trace as, in this case, I history-merged Omaha, Nebraska with Omaha (disambiguation). Graham87 (talk) 10:20, 22 May 2025 (UTC)