blob: c26a0e7cd5a729ed24f9d7b642e1f48a078efbbe (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Freeze push: libmtp
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Freeze%20push%3A%20libmtp&In-Reply-To=%3C5155BF1D.5010906%40damsweb.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="023990.html">
<LINK REL="Next" HREF="023969.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Freeze push: libmtp</H1>
<B>Damien Lallement</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Freeze%20push%3A%20libmtp&In-Reply-To=%3C5155BF1D.5010906%40damsweb.net%3E"
TITLE="[Mageia-dev] Freeze push: libmtp">mageia at damsweb.net
</A><BR>
<I>Fri Mar 29 17:19:41 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="023990.html">[Mageia-dev] Help needed with <..> oar
</A></li>
<LI>Next message: <A HREF="023969.html">[Mageia-dev] Freeze push: libmtp
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23956">[ date ]</a>
<a href="thread.html#23956">[ thread ]</a>
<a href="subject.html#23956">[ subject ]</a>
<a href="author.html#23956">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Please submit libmtp 1.1.6 (1.1.5 for now):
A bug fix and improvements release.
Changes from 1.1.5 to 1.1.6:
- Soname libmtp.so.9.1.0 - binary compatible, new interfaces
have been added.
- Devices, devices, devices... I think I had a hundred (no kidding)
reports for the Nexus 4. It seems hackers just love this device
and cannot wait for me to spin a new libmtp.
- More careful autoprobing code for Linux, running around in
sysfs to try to avoid opening non-MTP devices. The libusb devs
do not uniformly like this idea but what shall I do? People
still want their devices to autodetect. Any hints welcome,
any patches will be reviewed.
- Interface extenstions from Philip Langdale to support the
Android in-place read/write extensions. This will be used by
GVFS for editing files etc, it is actually very useful when
treating the MTP device as a "real" filesystem. It only works
on Android devices with Google's MTP stack, but hey, that is
a fair share of the MTP devices used today.
- Several fixes and memory leaks fixed by Lei Zhang courtesy if
the Chromebook project, thanks Google!
- Did you know that Microsoft silently dropped the MTPZ extension
from Windows Phone 8? Now you know. Newer Windows Phone
devices are reported to work out-of-the-box with libmtp.
Thanks!
--
Damien Lallement
twitter: damsweb - IRC: damsweb/coincoin
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="023990.html">[Mageia-dev] Help needed with <..> oar
</A></li>
<LI>Next message: <A HREF="023969.html">[Mageia-dev] Freeze push: libmtp
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23956">[ date ]</a>
<a href="thread.html#23956">[ thread ]</a>
<a href="subject.html#23956">[ subject ]</a>
<a href="author.html#23956">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
