RSB Git modified status

[Chris Johns]

On 19/04/2016 08:11, Gedare Bloom wrote:
> On Mon, Apr 18, 2016 at 5:31 PM, Chris Johns <chrisj at rtems.org> wrote:
>> This lets us know if the repo is clean or dirty and if changes have been
>> made. It helps us support users and it can be part of the evidence in an
>> audit.
>>
> For this specific use, I would not call it modified, because it is
> useful to differentiate between a tree that has actually been modified
> by a user, and a build that is "vanilla" with only modifications
> introduced by auto-gen files. Any untracked files present should only
> affect the build if the user also modifies tracked files (short of a
> user hacking Makefile.in and configure files, too).

This is what I also think. The RSB is unique because you can add a new 
file or a few files and use those but they would tend to result in 
different version numbers showing up in other parts.

I will push a patch.

Thanks
Chris