6

See Mootools events, callable?

Merging a question with itself probably shouldn't be possible. I tried rolling back to the original version, but that had no effect.

7
  • 2
    Argh, my head's spinning from the testing...
    – Andy E
    Commented Jul 16, 2010 at 12:35
  • 3
    @Andy: Imagine how long it took me to figure out what the problem was! ;) Commented Jul 16, 2010 at 12:45
  • @Popular Demand: There was a mod flag on that question asking for a tag merge. The wording might have been a little confusing, leading @Will to merge the question to itself. Either that, or idle curiosity would be my other guess. @Will wouldn't be the first one to experiment with the mod tools. :) Commented Jul 16, 2010 at 17:37
  • @Pop: Now they think about putting it before the name ... Commented Jul 16, 2010 at 19:29
  • 1
    @Bill: Are you able to manually unlock the question?
    – Jon Seigel
    Commented Jul 16, 2010 at 22:29
  • @Jon Seigel: Well now I just feel silly! Thanks. :) Commented Jul 17, 2010 at 1:37
  • @Bill: You're welcome. :)
    – Jon Seigel
    Commented Jul 17, 2010 at 2:17

2 Answers 2

2

ah, OK -- we checked in a change that prevents self-merges.

1
  • Oh, darn... sorry about the time spent on this one. It didn't occur to me that merging and locking were so closely intertwined. Commented Jul 17, 2010 at 3:40
1

I guess [status-by-design] is the best fit for this one. This is really a non-issue since the action is easily reversed by manually unlocking the question, as suggested by @Jon Seigel in the comments. Thanks Jon.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .