On 09/29/2015 04:25 AM, m. allan noah wrote:
I just pushed all of these. I did re-write the microtek2 patch to use
the logic I pointed out in a prior mail.
/meaning sequenced `% 2` changed to sequenced '!'/
Isn't this fancy-coding now, though?
I didn't look in the backend and may have
comple
I just pushed all of these. I did re-write the microtek2 patch to use
the logic I pointed out in a prior mail.
allan
On Mon, Sep 28, 2015 at 8:39 AM, Olaf Meeuwissen
wrote:
> Hi All(an),
>
> I've pushed a few new Proposed Upgrades (PU) to my GitLab clone[1].
>
> [1] https://gitlab.com/sane-proj
On Mon, Sep 28, 2015 at 7:04 AM, Johannes Meixner wrote:
>
> Hello,
>
> On Sep 28 18:59 Olaf Meeuwissen wrote (excerpt):
>>
>> With the sequencing issues, we can only speculate at what
>> the intended behaviour is, so we can't really fix things.
>> That notwithstanding, I think we can make a decen
Hi All(an),
I've pushed a few new Proposed Upgrades (PU) to my GitLab clone[1].
[1] https://gitlab.com/sane-project/backends/branches
I know that there are some restrictions on what can go in at this point
but I will leave that to the discretion of whomever merges them. Apart
from the first PU
Olaf Meeuwissen writes:
> Johannes Meixner writes:
>
>> Hello,
>
> Hi Johannes,
>
>> On Sep 28 18:59 Olaf Meeuwissen wrote (excerpt):
>>> With the sequencing issues, we can only speculate at what
>>> the intended behaviour is, so we can't really fix things.
>>> That notwithstanding, I think we ca
Johannes Meixner writes:
> Hello,
Hi Johannes,
> On Sep 28 18:59 Olaf Meeuwissen wrote (excerpt):
>> With the sequencing issues, we can only speculate at what
>> the intended behaviour is, so we can't really fix things.
>> That notwithstanding, I think we can make a decent, educated
>> guess at
Hi,
Thank's for your answer.
Am 26.09.2015 um 18:33 schrieb Stef:
>
> have you tried to tweak genesys frontend's analog gain ? Exposure
> is also related to motor speed, and will be really complicated to set up.
Hmm, yea, I was afraid of this - the link between Motor-Drive and Exposure .
I d
Hello,
On Sep 28 18:59 Olaf Meeuwissen wrote (excerpt):
With the sequencing issues, we can only speculate at what
the intended behaviour is, so we can't really fix things.
That notwithstanding, I think we can make a decent, educated
guess at a fix for both cases and make the warning go away :-|
m. allan noah writes:
> I think we are all on the same page here regarding clarity of code,
> and our concern over warnings. Long term, it would be great if sane
> were warning free- but that would require that code get maintainers,
> or get ejected. Given that some scanners we support have not b
Johannes Meixner writes:
> Hello,
>
> On Sep 25 21:02 Olaf Meeuwissen wrote (excerpt):
>> In the
>> mean time, I think we should any code that is flagged as -Wunsequenced
>> (by clang) or -Wsequence-point (by gcc).
>
> I assume the meaning is clear but there is an omission.
> What exactly should b
m. allan noah writes:
> On Thu, Sep 24, 2015 at 9:22 AM, Olaf Meeuwissen
> wrote:
>>
>> Anyway, please consider merging the pu/ branches at my GitLab clone.
>
> These all made sense to me, so I pushed them up. Thanks for doing the
> legwork here.
Thanks. I've removed the branches from my GitLab
11 matches
Mail list logo
