summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Drake <dsd@gentoo.org>2009-08-01 13:55:15 +0545
committerDaniel Drake <dsd@gentoo.org>2009-08-01 13:56:11 +0545
commit45ae2aecf5512dcff059b2a416534e81c6a00c88 (patch)
treec57d25b74c2abceadeeabe312b0e75cb60571e17
parent126129e174062c2a27423817a459e5113f777789 (diff)
downloadlibusb-45ae2aecf5512dcff059b2a416534e81c6a00c88.tar.gz
move bug info to bug tracker
Protection needed: http://www.libusb.org/ticket/4 Losing data: fixed in previous commit
-rw-r--r--BUGS10
-rw-r--r--Makefile.am2
2 files changed, 1 insertions, 11 deletions
diff --git a/BUGS b/BUGS
deleted file mode 100644
index 2d40b5a..0000000
--- a/BUGS
+++ /dev/null
@@ -1,10 +0,0 @@
-- Linux: Races are suspected to occur in multi-threaded applications when
- cancelling transfers while there is an event handler in progress.
- Variables like reap_action need protection. This needs some careful thought
- and testing.
-
-- Linux: data can be lost when transfers are cancelled. libusb incorrectly
- assumes that transfers are always empty when they are reaped after
- cancellation. It should move the data to the correct point in the buffer --
- while still inconvenient for the application developer, it's better than
- losing it altogether.
diff --git a/Makefile.am b/Makefile.am
index 8b90df0..284cdbb 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -1,7 +1,7 @@
AUTOMAKE_OPTIONS = dist-bzip2
ACLOCAL_AMFLAGS = -I m4
DISTCLEANFILES = ChangeLog libusb-1.0.pc
-EXTRA_DIST = TODO PORTING BUGS
+EXTRA_DIST = TODO PORTING
SUBDIRS = libusb doc
if BUILD_EXAMPLES