Sansa Fuze v2 installed build

[Datman]

Hi,
on my H120 I can read the Rockbox installed build at startup, but I don't see it in the Fuze v2. Where can I find it?

Thanks.
Gianluca

[saratoga]

System -> rockbox info.

[Datman]

Thank you for your reply, Saratoga. I've already looked there, but I only read:

Battery:72% 15h 13m
Int: 990MB/3.66GB
MSD: 5.46GB/7.47GB
Buffer: 5.65MB
Skin RAM usage: 162KB / 432KB
Version: 3.7

I don't see something like:

Ver: 3.7  r29005

[Llorean]

Version 3.7 is a specific single version outside of the normal revision series. Why would you expect it to have a revision number as well?

[Datman]

Then r29005 is the (unofficial?) revised 3.7...
Thanks
G.

Ok. I've updated to r29005.

[[Saint]]

A release build is just a snapshot from the SVN repository at a specific moment in time.

r29005 is the very latest (as of this writing) SVN revision, and 3.7 was tagged at r28402

r29005 isn't the "unofficial" anything, it's simply one of the *many* revisions made to the repository on a daily basis.

Every so often, new additions are to the repository are "frozen" for a release, and for ~2 weeks or so developers attempt to work on outstanding issues in preparation for tagging another release.


[St.]

[Datman]

Thank you, St.

[Llorean]

r29005 is the very latest (as of this writing) SVN revision, and 3.7 was tagged at r28402

Just to clarify, this does not mean that 3.7 is r28402. If you check out 28402 and build it, what you'll get is something different than version 3.7. Any given release version may have special changes that are unique to the release such as disabling unstable features, or patches that may revert an unstable change that isn't reverted in the main build or other such changes. I can't speak for what is unique in 3.7 specifically, but there's always a release "branch" of the code, and just going by revision number will not get you an identical build to the release.