Repo to analyze and measure the azure IoTHub C SDK code base

Перейти к файлу

jebrando 38a17630d7 Update parson repo to latests		2019-05-20 08:50:32 -07:00
app_analysis	Initial start for app_analysis	2018-11-16 18:11:15 -08:00
binary_info	Update repo for submodule renames	2019-05-20 08:41:41 -07:00
certs	Initial Checkin for repo	2018-02-07 16:56:54 -08:00
configs	Initial Checkin for repo	2018-02-07 16:56:54 -08:00
deps	Update parson repo to latests	2019-05-20 08:50:32 -07:00
docs	Add provisioning dps information to repo	2018-02-27 17:42:54 -08:00
memory	Initial start for app_analysis	2018-11-16 18:11:15 -08:00
network	Added way to include connection header	2019-01-10 08:55:48 -08:00
script	Uncomment make command	2019-01-10 13:12:56 -08:00
.gitignore	Initial Checkin for repo	2018-02-07 16:56:54 -08:00
.gitmodules	Update reporter to start using handles	2018-09-03 11:57:36 -07:00
CMakeLists.txt	Update repo for submodule renames	2019-05-20 08:41:41 -07:00
LICENSE	Initial commit	2018-01-29 14:22:27 -08:00
README.md	Initial commit	2018-01-29 14:22:28 -08:00
binary_results.txt	Update binary file information	2018-09-14 17:27:56 -07:00
jebrado-tres_bin_results.txt	Update memory information for reporter	2018-09-14 14:27:34 -07:00
mem_reporter.c	Initial start for app_analysis	2018-11-16 18:11:15 -08:00
mem_reporter.h	Initial start for app_analysis	2018-11-16 18:11:15 -08:00

README.md

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.