On Thu, Mar 31, 2016 at 1:32 PM, Marco Martin wrote:
> On Thursday 31 March 2016, Dominik Haumann wrote:
>> > Still, if you get regressions with respect to pluggable mtp devices,
>> > please let me know.
>>
>> Again me ;)
>>
>> Since Applications/16.04 seems to be already branched, is it ok to
>>
On Thursday 31 March 2016, Dominik Haumann wrote:
> > Still, if you get regressions with respect to pluggable mtp devices,
> > please let me know.
>
> Again me ;)
>
> Since Applications/16.04 seems to be already branched, is it ok to
> cherry-pick this commit?
i think so, as it's a fix
--
Marc
On Thu, Mar 31, 2016 at 1:01 PM, Dominik Haumann wrote:
> On Thu, Mar 31, 2016 at 12:55 PM, Marco Martin wrote:
>> On Thursday 31 March 2016, Dominik Haumann wrote:
>>
>>> Since the 16.04 release is about to happen, can we still get this
>>> change committed? For close to two weeks I got no reply
On Thu, Mar 31, 2016 at 12:55 PM, Marco Martin wrote:
> On Thursday 31 March 2016, Dominik Haumann wrote:
>
>> Since the 16.04 release is about to happen, can we still get this
>> change committed? For close to two weeks I got no reply/review.
>>
>> That's rather unfortunate, since imo the patch i
On Thursday 31 March 2016, Dominik Haumann wrote:
> Since the 16.04 release is about to happen, can we still get this
> change committed? For close to two weeks I got no reply/review.
>
> That's rather unfortunate, since imo the patch is ready and correct
> (even confirmed by the libmtp authors t
