On 11.02.2014 01:56, mrnuke wrote:
On Tuesday, February 11, 2014 12:04:33 AM Vladimir 'φ-coder/phcoder' Serbinenko wrote:
If we let user supply files at all, it should be added to report, not replace files, and it should have some prefix to clearly indicate that user was involved in creating them. E.g. user_serial_log.txt
There is a point at which the information becomes "too much". What is really relevant, in my opinion, are the following three points:
- Is it an unmodified commit in master (AKA, not "-dirty").
- Does it boot?
- What does not work, if any ?
Point 1 and 2 are answered by "cbmem -c | head". It answers point 1 with the first line of output, and point 2 by the fact that getting anything from cbmem means you've already booted your system.
Point 3 is more complicated, and it seems it is because of this point that we want to collect any and all information we can possibly get our hands on.
Other than "cbmem -c | head" and .config, a majority of people just don't care about all the pesky details. They're only useful when debugging problems some poor guy or gal is having. In that case, we can ask them for this info manually. It's not of any use in tracking down which revision + config works on _this_ board.
This is not the only uses of board-status. It's also useful to see if some boards have an issue which one meets in particular board. This information is important in tracking bugs down but hard to collect unless it's in the board-status.