> If the .version file is not present, the Makefile
> creates a dummy .version with version number 0.0.0. That is not a useful
> version number and effects the OS identification in all of the above uses.
This only happens when the .git directory is also not present, i.e. we
are using a release tar
Now, the question is, does the .release file exist only on release
branches or also in master?
It was also exist in master as I described it.
If in master, then I think the .release file would need to be
incremented on 'master' immediately after branching for a release. So,
for example, immed
On Tue, Apr 21, 2020 at 10:49 AM Gregory Nutt wrote:
>
> When we do a release, the zipme script creates a proper version of the
> .version file. This later becomes the version.h header file and is used
> in several places:
>
> 1. NSH Greeting
> 2. libcurl (OS identity)
> 3. webserver (OS ident
When we do a release, the zipme script creates a proper version of the
.version file. This later becomes the version.h header file and is used
in several places:
1. NSH Greeting
2. libcurl (OS identity)
3. webserver (OS identity)
4. procfs version file
5. uname OS version number
The .version
