I'm doing some tests with an experimental code that counts cyclists in the cycle range, for these tests I'm using gprof and gcov that generate several analysis files, one of these files generated by gprof I'm sending to the versioning repository to maintain a history of code improvement.
What other files should I upload too? What file structure should I use for such optimization history and profiling reports.
Delfino,
As a general rule, it is not normal for you to put data collected from a build, for example, or test results; in version control. Normally this type of data enters OLAP database, or as input from a tool. I do not know these types of files, however, I imagine you will use some tool to read this data, if it will get version control, it would be interesting to create a new repository just for that data, or it will burden the code repository, causing developers to download unnecessary files to development and large size. If the source for the analysis is neither the git repository, this file should not be placed there. It would be bad practice.
