0
I am doing some tests with an experimental code that makes count of cyclists in the bike lane, for these tests I am using the gprof and gcov that generate several analysis files, one of these acquisitions generated by gprof I am sending to the versioning repository to keep track of code improvement.
Should I send the other files as well? What file structure should I use for such optimization history and Profiling reports.
2
Delfino,
As a rule, it is not normal for you to put collected data from a build, for example, or from test results; in version control. Usually this type of data enters a OLAP database, or as input from a tool. I don’t know these types of files, but I imagine that you will use some tool to read this data, if it will get from version control, it would be interesting to create a new repository only for this data, or it will burden the code repository, causing developers to download files that are unnecessary for development and large in size. If the source for the analysis is not even the git repository, this file should not be placed there. It would be bad practice.
Browser other questions tagged git github gcc
You are not signed in. Login or sign up in order to post.
the file is a common txt with several annotations, the raw files do not think to put are actually binary and generated locally, although they can be unified for a later analysis. I thought I’d put it as a submodule, but it falls into the same question of having excess material to download, a remote database is not viable, and a file sharing tool like Dropbox I don’t know if it would because it wouldn’t control multiple users by updating the same files.
– Delfino
Why is a remote database not feasible? Or even a location, being manually synchronized
– egomesbrandao
I do not have the database, and the file is only a TXT file, and the use of cloud does not give opening for everyone to change with versioning the files, Suggestions are welcome.
– Delfino