[Pidgin] #4755: Propagate t:v2.4.0 to im.pidgin.soc.2007.msimprpl

[Pidgin]

#4755: Propagate t:v2.4.0 to im.pidgin.soc.2007.msimprpl
----------------------+-----------------------------------------------------
  Reporter:  jeff     |       Owner:  jeff 
      Type:  defect   |      Status:  new  
  Priority:  major    |   Milestone:       
 Component:  MySpace  |     Version:  2.3.1
Resolution:           |    Keywords:       
   Pending:  0        |  
----------------------+-----------------------------------------------------
Comment (by rekkanoryo):

 In this case, just do:

 `mtn approve -b im.pidgin.soc.2007.msimprpl
 218736e5b624dd2cb7fbba54b6cb8523645fff9b`

 You could also simply make changes in an `im.pidgin.pidgin` working copy
 but commit them with `mtn commit -b im.pidgin.soc.2007.msimprpl` to
 achieve the same result.  Doing this will change the branch of your
 working copy to `im.pidgin.soc.2007.msimprpl`.

 Your branch was propagated to `im.pidgin.pidgin` long ago and has had no
 activity since, thus there is no divergence and no need for a merge.  If
 you had simply run `mtn propagate`, it would have told you as much and
 simply added the branch cert to whichever revision was the head of
 `im.pidgin.pidgin` at the time.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/4755#comment:2>
Pidgin <http://pidgin.im>
Pidgin