2012/5/6 Pete Batard :
> And this was exactly my intention. The bulk of the patch is yours, and
> I don't really see the need to split it when the addon is minimal.
Pete, to avoid any more problems in the future maybe you should
refrain from editing patches from others.
I have no problem in havin
On Mon, May 7, 2012 at 8:40 AM, Pete Batard wrote:
> Libusbx v1.0.11 RC1 is now available either from git, or as a source
> tarball from:
> https://sourceforge.net/projects/libusbx/files/releases/1.0.11/source/
>
> This is the RC for the 1.0.11 bugfix release, that reverts the
> removal of critica
On 2012.05.07 09:22, Ludovic Rousseau wrote:
> Pete, to avoid any more problems in the future maybe you should
> refrain from editing patches from others.
If you think there ever was a problem, then Peter successfully managed
to make you believe that he had a say as to the content of the patch or
On Sun, May 6, 2012 at 10:39 AM, Xiaofan Chen wrote:
> On Sun, May 6, 2012 at 7:35 AM, Pete Batard wrote:
>> With BSD support becoming a headache, and no official
>> maintainer for the *BSD backends to help us out, along with
>> the need to go to bugfix release soon, I propose dropping
>> thread
Pete Batard wrote:
> If you think there ever was a problem,
Maybe Ludovic's point is that it would be nice to track authorship in
more detail than you care to.
> then Peter successfully managed to make you believe that he had a
> say as to the content of the patch or the commit message
I wrote
How about moving on to discuss things that actually move
the project forward...
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how
On 2012.05.07 12:32, Xiaofan Chen wrote:
There is one minor warning under OpenBSD (5.1 Current).
CCLD xusb
xusb.o(.text+0x10a3): In function `main':
/home/mcuee/Desktop/build/libusbx/libusbx-1.0.11-rc1/examples/xusb.c:781:
warning: strcat() is almost always misused, please use strlcat()
I
On 2012.05.07 14:40, Xiaofan Chen wrote:
> As per Matin (the author of the OpenBSD backend), you can
> use the getthrid() syscall that returns a pid_t.
Great. I'll give it a try and if it works, add it for the release.
Regards,
/Pete
-
On 2012.05.07 15:47, Pete Batard wrote:
> On 2012.05.07 14:40, Xiaofan Chen wrote:
>> As per Matin (the author of the OpenBSD backend), you can
>> use the getthrid() syscall that returns a pid_t.
>
> Great. I'll give it a try and if it works, add it for the release.
Seems to require linking agains
On Mon, May 7, 2012 at 10:45 PM, Pete Batard wrote:
> On 2012.05.07 12:32, Xiaofan Chen wrote:
>> There is one minor warning under OpenBSD (5.1 Current).
>> libusbx-1.0.11-rc1/examples/xusb.c:781:
>> warning: strcat() is almost always misused, please
>> use strlcat()
>
> I am also testing with Ope
On Mon, May 7, 2012 at 8:40 AM, Pete Batard wrote:
> Libusbx v1.0.11 RC1 is now available either from git, or as a source
> tarball from:
> https://sourceforge.net/projects/libusbx/files/releases/1.0.11/source/
>
> This is the RC for the 1.0.11 bugfix release, that reverts the removal
> of critica
On Sat, May 5, 2012 at 3:18 PM, Hans de Goede wrote:
>>> libusbx is already calling pthread_setname_np() for the thread it creates.
>>
>> But only for OS X I assume...
>>
>
> Sean, maybe it would be an idea for the os dependent code to print a
> thread "name" + id when creating a thread and debugg
On Sat, May 5, 2012 at 1:02 AM, Tim Roberts wrote:
> Janko Kolar wrote:
>> I am new to libusbx and I have one basic question
>>
>> I would like to determine to which usb port particular device is attached.
>
> Why? Of what possible use is this information? USB hubs are not
> externally labeled.
This may be good to be indexed in the libusbx mailing list as well.
Whole thread:
http://libusb.6.n5.nabble.com/FreeBSD-libusb-missing-libusb-get-descriptor-td5689243.html
Regards,
Xiaofan
-- Forwarded message --
From: Peter Stuge
Date: Mon, May 7, 2012 at 10:47 PM
Subject: Re:
I'll just add my opinion on parameter checking...
Anyone remember the "User Application Error" that old Windows versions used
to pop up? It was Microsoft's attempt to deflect blame for exactly the
same kind of crash in the Windows environment - most likely the user had
passed in a bad pointer (of
On Mon, May 7, 2012 at 11:16 PM, Pete Batard wrote:
> On 2012.05.07 15:47, Pete Batard wrote:
>> On 2012.05.07 14:40, Xiaofan Chen wrote:
>>> As per Matin (the author of the OpenBSD backend), you can
>>> use the getthrid() syscall that returns a pid_t.
>>
>> Great. I'll give it a try and if it wor
16 matches
Mail list logo
