On Mon, Aug 24, 2015 at 7:53 AM, Benjamin wrote:
> Would it not be best to include the firmware upgrade id anyway in a
> different section? At some stage people will want to upgrade the software
> anyway, so it might save questions in the future...
Sure, it would. However, I was thinking that we
Would it not be best to include the firmware upgrade id anyway in a
different section? At some stage people will want to upgrade the software
anyway, so it might save questions in the future...
Benjamin
___
subsurface mailing list
subsurface@subsurface-
Adding Linus' instructions for udev rule to our FAQ. Product ID 0031
that is used for firmware updates is not included here, as it is
probably not commonly needed.
Signed-off-by: Miika Turkia
---
Documentation/FAQ.wordpress | 12
1 file changed, 12 insertions(+)
diff --git a/Docume
On Sun, Aug 23, 2015 at 6:29 PM, Steve Butler wrote:
> Anybody on the list using Subsurface on Ubuntu 15.04 and downloading from an
> Eon Steel? If so, how did you get around the permission denied message?
> Better yet, what /dev/ are you using to do the download?
I'm not on Ubuntu, but the
Anybody on the list using Subsurface on Ubuntu 15.04 and downloading
from an Eon Steel? If so, how did you get around the permission denied
message? Better yet, what /dev/ are you using to do the download?
Part of dmesg output:
[ 13.505232] wlan0: associated
[ 167.332583] usb 1-1: new
Robert,
On 24 August 2015 at 01:25, Robert C. Helling wrote:
> Rick,
>
> On 22 Aug 2015, at 07:15, Rick Walsh wrote:
>
> To show what this actually does to the calculated profiles, I have made a
> new column on the Google docs spreadsheet Robert set up.
>
> This gets the calculated profiles not
Signed-off-by: Miika Turkia
---
tests/testparse.cpp | 72 +++--
1 file changed, 65 insertions(+), 7 deletions(-)
diff --git a/tests/testparse.cpp b/tests/testparse.cpp
index fa1d6d2..f12ac36 100644
--- a/tests/testparse.cpp
+++ b/tests/testparse.cp
This removes the excessive amount of parameters on manual CSV import. We
just use appropriate string array than can be directly fed to XSLT
parsing.
Signed-off-by: Miika Turkia
---
dive.h| 3 +-
file.c| 128 +++
Signed-off-by: Miika Turkia
---
dive.h| 2 +-
file.c| 29 +++--
qt-ui/divelogimportdialog.cpp | 60 ++-
3 files changed, 58 insertions(+), 33 deletions(-)
diff --git a/dive.h b/dive.h
index e
Signed-off-by: Miika Turkia
---
tests/testparse.cpp | 56 -
1 file changed, 38 insertions(+), 18 deletions(-)
diff --git a/tests/testparse.cpp b/tests/testparse.cpp
index f12ac36..76b3912 100644
--- a/tests/testparse.cpp
+++ b/tests/testparse.c
Rick,
> On 22 Aug 2015, at 07:15, Rick Walsh wrote:
>
> To show what this actually does to the calculated profiles, I have made a new
> column on the Google docs spreadsheet Robert set up.
>
> This gets the calculated profiles noticeably closer to those calculated by
> other software, except
On Sun, Aug 23, 2015 at 07:31:48AM -0700, Dirk Hohndel wrote:
> Thanks for adding the test.
>
> I think it's rather educational how many little things one runs into when
> creating a test. That alone is useful - and of course having the test then
> allows us to notice when we unintentionally break
Thanks for adding the test.
I think it's rather educational how many little things one runs into when
creating a test. That alone is useful - and of course having the test then
allows us to notice when we unintentionally break things... assuming I can
remember to always run the tests before pushin
From 449468f3445c5523ee7c4d4a46c6162db60a7095 Mon Sep 17 00:00:00 2001
From: "Robert C. Helling"
Date: Sun, 23 Aug 2015 15:58:50 +0200
Subject: [PATCH 1/5] Show tissue ceilings in tenth of m/ft
Signed-off-by: Robert C. Helling
---
profile.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Rick,
> On 23 Aug 2015, at 15:18, Rick Walsh wrote:
>
> Yes, there are very small ceiling violations in some cases I've tried. If
> you can't devise a precise method to calculate a gradient that agrees exactly
> with the planned dive, we could relax the definition of a ceiling violation
> to
On 23 August 2015 at 18:52, Robert C. Helling wrote:
> Hi,
>
> On 23 Aug 2015, at 00:25, Rick Walsh wrote:
>
> Note that to my knowledge this only occurs calculating the ceiling for
> profile.c, not when calculating the plan. Yes, I'm repeating myself but
> that could save hours of debugging.
>
Hi,On 23 Aug 2015, at 00:25, Rick Walsh wrote:Note that to my knowledge this only occurs calculating the ceiling for profile.c, not when calculating the plan. Yes, I'm repeating myself but that could save hours of debugging.here is another attempt. This at least computes the
Hi,
> On 22 Aug 2015, at 07:15, Rick Walsh wrote:
>
> To show what this actually does to the calculated profiles, I have made a new
> column on the Google docs spreadsheet Robert set up.
>
> This gets the calculated profiles noticeably closer to those calculated by
> other software, except fo
18 matches
Mail list logo