On 25/03/14 00:05, Richard Fuchs wrote:
On 03/22/14 04:55, Peter Lemenkov wrote:
2014-03-21 20:04 GMT+04:00 Richard Fuchs <[email protected]>:
Since we're slowly running out of flag letters :) we'd like to take this
opportunity to revamp the flag handling within the module, break
backwards compatibility with the original rtpproxy module interface, and
rename both rtpproxy-ng and mediaproxy-ng (starting with version 3.0) to
rtpEngine, in an attempt to clean up the unfortunate naming conventions
between the two.
Great news! This will simplify a lot of things. Hope you won't use
camelCase in the official name :)
No camelCase, at least not in the module/function names :D
So how do I go about renaming? Just like that, or should I leave a
README in the old directory, pointing to the renamed module, or...?
Just rename it, don't keep anything from old one in place.
You can use 'git mv ...' to keep the track in the history.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference - April 2-4, 2014, Berlin, Germany
http://www.kamailioworld.com
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
