On 07/10/13 15:12, Chris Bagwell wrote:
> On Thu, Oct 3, 2013 at 1:34 PM, Johannes Bauer
> wrote:
>> On 03.10.2013 13:12, m. allan noah wrote:
>>> I would recommend that you use git bisect (or a manual equivalent) to
>>> find the commit that breaks epson2. Then we can investigate a fix.
>> This i
On Thu, Oct 3, 2013 at 1:34 PM, Johannes Bauer wrote:
> On 03.10.2013 13:12, m. allan noah wrote:
>> I would recommend that you use git bisect (or a manual equivalent) to
>> find the commit that breaks epson2. Then we can investigate a fix.
>
> This is really messed up:
>
> 206e6ed094c080be903b154
On Thu, Oct 3, 2013 at 4:32 AM, Johannes Bauer wrote:
> Hi list,
>
> I have two scanners, one that uses the epson2 backend and a nex ScanSnap
> ix500 which uses the fujitsu. For the newer ix500 I needed a fairly
> recent version, so I'm currently using git head of sane-backends. This
> report conc
On 03.10.2013 13:12, m. allan noah wrote:
> I would recommend that you use git bisect (or a manual equivalent) to
> find the commit that breaks epson2. Then we can investigate a fix.
This is really messed up:
206e6ed094c080be903b154ea3d016cc226feb89 is the first bad commit
commit 206e6ed094c080be
Hi list,
I have two scanners, one that uses the epson2 backend and a nex ScanSnap
ix500 which uses the fujitsu. For the newer ix500 I needed a fairly
recent version, so I'm currently using git head of sane-backends. This
report concerns 472daf78.
First note: the epson2 backend doesn't compile, be
I would recommend that you use git bisect (or a manual equivalent) to
find the commit that breaks epson2. Then we can investigate a fix.
allan
On Thu, Oct 3, 2013 at 5:32 AM, Johannes Bauer wrote:
> Hi list,
>
> I have two scanners, one that uses the epson2 backend and a nex ScanSnap
> ix500 whi
