projects / gpsbabel.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 50b16e9) | patch
The lezyne "super gps", every 10th ride or so, outputs a .fit file that is entirely...
authorTim Connors <tconnors@rather.puzzling.org>
Sat, 14 Sep 2019 12:06:06 +0000 (22:06 +1000)
committerJochen Sprickerhof <jspricke@debian.org>
Tue, 24 Sep 2019 20:09:09 +0000 (21:09 +0100)
commit0e1b55e064e06189b9e7714115e58a9fceb3f73c
tree0a501d59c67c162660ec4ff5b9783c39da86049ftree | snapshot
parent50b16e9cda38f5049b35563b8015398e8f1618cdcommit | diff
The lezyne "super gps", every 10th ride or so, outputs a .fit file that is entirely valid other than a weird non 0/1 endian field. Don't dump the data just because of that.

Gbp-Pq: Name 0012-The-lezyne-super-gps-every-10th-ride-or-so-outputs-a.patch
garmin_fit.cc diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.