Maybe @api could be a subset of the @feature. This means from time to time we need to add @api, @feature at the same time. Also, If a huge api set is going to be added for a new feature, then commit message will be too long.
But I have no objection if it could be helpful for researching api changes. by the way, thanks for python bindings. ------------------------------------ -Regards, Hermet- -----Original Message----- From: "Davide Andreoli"<d...@gurumeditation.it> To: "enlightenment-devel"<enlightenment-devel@lists.sourceforge.net>; Cc: Sent: 2014-03-02 (일) 03:54:28 Subject: [E-devel] Request two new tag for commit message Hi all, I just finished now to port all the API additions of efl 1.9 to the python bindings, it has been quite a hell to go through all the commits to search what has been added and what has been deprecated. So I'm going to propose/ask two more tags for commit messages: @api and @deprecated Usage example for a commit where you added 2 new api and deprecate one: @api Elm_Object_Item *elm_object_focused_item_get(const Evas_Object *obj); @api void elm_object_item_focus_set(Elm_Object_Item *it, Eina_Bool focused); @deprecated elm_object_old_function_name(params...); This has also the advantage to clarify to all the readers what has been added at the api level so that we can spot earlier bad designed names and params. The @api tags should also be used for added signals, example: @api elm_button: "item,unfocused" Like the idea? davemds ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
