Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 6 commits
- 6 files changed
- 2 contributors
Commits on Mar 5, 2023
Commits on Apr 4, 2023
Commits on Nov 23, 2023
-
The issue arises due to the reMarkable software version no longer being accurately reflected in `/etc/version`. This causes rmview to think it is connecting to an older version. I've fixed this by switching rmview's SW version logic over to the semantic versioning scheme used by recent releases. The SW version is taken from the `REMARKABLE_RELEASE_VERSION` value in `/usr/share/remarkable/update.conf`, as suggested by @Eeems. Support for older versions is to be maintained by mapping the older timestamp version numbers back to the corresponding semantic versions.
-
Added additional catch-all case for timestamp based versioning
Prior commit reported version 2.9.1.236 for all timestamps greater-than or equal to the 2.9.1.236 timestamp. I realized this might break the versioning logic for later 2.9 SW versions, so I added an additional version tuple of (2.9.1.9999) to represent those versions instead.
Commits on Dec 11, 2023
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.1.2...v3.1.3