Hi All,
With Derek's patch, the documentation for destiny branch is more
useful for those using Python. Consequently, I have pushed the
doxygen documentation for destiny (which include Derek's patch) to
replace the one previously generated from zaku. FYI.
Regards
KK
On 11 January 2011 11:43, kk yap <yap...@stanford.edu> wrote:
> Hi Derek,
>
> Thanks. Great patches as usual. I have pushed them to the destiny branch.
>
> Martin and Murphy, I believe I have pushed most (if not all) of
> Derek's patches at this moment. If anything else is missing, let me
> know.
>
> Thanks.
>
> Regards
> KK
>
> On 11 January 2011 07:23, Martin Casado <cas...@nicira.com> wrote:
>> Derek,
>>
>> Thanks for the patches, these are very helpful. One of us will take a look
>> shortly.
>>
>> .martin
>>
>> Hello,
>> Here are two patches for destiny for the Python API.
>>
>> patch 1:
>> - in pyrt.cc, add datapath id to the dictionaries created by
>> Flow_removed_event and Error_event
>>
>> patch2:
>> - add lots of doxygen doc strings to core.api
>> - add callback generators for flow mod and flow removed events
>> - change the names of callback generators to make them more readable
>> - add more constants for dictionary keys
>>
>> -Derek
>>
>> On 01/04/2011 10:27 AM, kk yap wrote:
>>
>> Hi Derek,
>>
>> Thanks. Doxygen comments are presented in the code. E.g.,
>>
>> /** \brief Event
>> * Some event
>> *
>> * @author ykk
>> * @date Jan 2011
>> */
>> struct x_event
>> {
>> ...
>> }
>>
>> They are more in-depth example in the components.
>>
>> Regards
>> KK
>>
>> On 3 January 2011 17:19, Derek Cormier<derek.corm...@lab.ntt.co.jp> wrote:
>>
>> Sure thing. Where do the doxygen comments go? I've never used doxygen
>> before, I'm assuming they go above the struct definition but I don't see any
>> such comments in the files I edited. Is there another file?
>>
>> Thanks,
>> -Derek
>>
>> On 01/04/2011 06:20 AM, kk yap wrote:
>>
>> Hi Derek,
>>
>> Sorry it took me a while to get to this. Can you put in doxygen
>> comments for these patches? The patches includes new structs and so
>> on from what I can see. Else, I can do it. But I doubt I can get to
>> it fast enough. Thanks.
>>
>> Regards
>> KK
>>
>> On 27 December 2010 23:23, Derek Cormier<derek.corm...@lab.ntt.co.jp>
>> wrote:
>>
>> Here's a couple more patches for destiny.
>>
>> 'barrier-reply.tar.gz' - make barrier reply events available to the
>> Python
>> API.
>> 'flow-stats-in.tar.gz' - add a convenience method in component to
>> register
>> for flow stats in events.
>>
>> -Derek
>>
>> On 12/28/2010 01:30 AM, Martin Casado wrote:
>>
>> Thanks KK. I pushed a few edits as well.
>>
>> Hi,
>>
>> I have done that for destiny and pushed the file. Martin, you should
>> probably check the list again. If I have missed you out (since I only
>> exploited git log), do let me know.
>>
>> Regards
>> KK
>>
>> _______________________________________________
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>
>>
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Martin Casado
>> Nicira Networks, Inc.
>> www.nicira.com | www.openvswitch.org
>> cell: 650-776-1457
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
