Re: [gphoto-devel] storage/handle error

2018-03-18 Thread Marcus Meissner
On Wed, Mar 14, 2018 at 09:58:03PM +0100, Marcus Meissner wrote: > On Wed, Mar 14, 2018 at 09:37:38PM +0300, Alexey Kryukov wrote: > > On Wed, 14 Mar 2018 08:44:17 +0100 > > Marcus Meissner wrote: > > > > > sorry, now pushed out. > > > > Thanks! By the way, have you seen my second patch for EOS M

Re: [gphoto-devel] storage/handle error

2018-03-18 Thread Marcus Meissner
On Sat, Mar 10, 2018 at 09:00:08PM +0300, Alexey Kryukov wrote: > On Thu, 8 Mar 2018 22:52:56 +0100 > Marcus Meissner wrote: > > > I disabled the error again in git, it appeared after the event > > additgion I think. > > ...however still there is no update in git (at least I can't see it)? sorry

Re: [gphoto-devel] storage/handle error

2018-03-14 Thread Marcus Meissner
On Wed, Mar 14, 2018 at 09:37:38PM +0300, Alexey Kryukov wrote: > On Wed, 14 Mar 2018 08:44:17 +0100 > Marcus Meissner wrote: > > > sorry, now pushed out. > > Thanks! By the way, have you seen my second patch for EOS M2? yes, but i need to find a spare hour to review and test... this is a bit ra

Re: [gphoto-devel] storage/handle error

2018-03-14 Thread Alexey Kryukov
On Wed, 14 Mar 2018 08:44:17 +0100 Marcus Meissner wrote: > sorry, now pushed out. Thanks! By the way, have you seen my second patch for EOS M2? -- Regards, Alexey Kryukov Moscow State University Faculty of History -

Re: [gphoto-devel] storage/handle error

2018-03-10 Thread Alexey Kryukov
On Thu, 8 Mar 2018 22:52:56 +0100 Marcus Meissner wrote: > I disabled the error again in git, it appeared after the event > additgion I think. ...however still there is no update in git (at least I can't see it)? -- Regards, Alexey Kryukov Moscow State University Faculty of History -

Re: [gphoto-devel] storage/handle error

2018-03-08 Thread Marcus Meissner
On Thu, Mar 08, 2018 at 06:17:41PM +0300, Alexey Kryukov wrote: > Hi, > > running gphoto2 with libgphoto2 from the current git I always (and with > different cameras) get the following error message: > > storage 0x, but handle 0x? > > As far as I can see from ptp.c, the program f