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 critical Windows event handling call, which was introduced in 1.0.10
On 2012.05.07 00:43, Xiaofan Chen wrote:
> So I actually want to get the simple
> VID/PID filter done first which you agree in your first reply
> that "as Segher's suggest is a no brainer, and, IIRC, we used to
> have something similar in the 0.1 API, so I'm fine with that".
>
> BTW, there is nothi
On Mon, May 7, 2012 at 6:02 AM, Pete Batard wrote:
> On 6 May 2012 15:32, Xiaofan Chen wrote:
>> I think maybe it is a good idea to extend the discussion
>> to a bigger group now that libusbx-devel is open to the public.
>
> Which is also what I want. But I also want to make sure that both
> side
On 2012.05.06 23:56, Peter Stuge wrote:
>> Then please define full owership.
>
> --8<-- http://simple.wikipedia.org/wiki/Copyright
> A copyright is a law that gives the owner of a written document,
> musical composition, book, picture, or other creative work, the right
> to decide what other people
Peter Stuge wrote:
> >From your email it's clear to me that we agree on how this works!
No I didn't. The email I sent did not have a leading >. I haven't
seen this happen to me before. It may be an SF problem. I've seen it
happen with patches on libusb-devel. I'm investigating.
//Peter
Pete Batard wrote:
> > I remain the author of my work with all that it entails including
> > full ownership of my work
>
> Then please define full owership.
--8<-- http://simple.wikipedia.org/wiki/Copyright
A copyright is a law that gives the owner of a written document,
musical composition, book
On 6 May 2012 15:32, Xiaofan Chen wrote:
> I think maybe it is a good idea to extend the discussion
> to a bigger group now that libusbx-devel is open to the public.
Which is also what I want. But I also want to make sure that both
sides are represented as they should and I don't see that happeni
On 6 May 2012 18:07, Peter Stuge wrote:
> Your proposed commit message says clearly what the commit adds to
> libusbx.git, but the difference between my work and yours is not
> clear while I am named as author with no mention of you, and that
> isn't really accurate.
Happens all the time on every
Pete Batard wrote:
> On 6 May 2012 00:52, Peter Stuge wrote:
> > Please clarify in the commit message what was changed since my
> > commit, and please mention the commit id in libusb.git.
>
> This is done in the subject. Thread ID was added. There's no need
> for more.
Your proposed commit messa
On Sun, May 6, 2012 at 10:03 PM, Pete Batard wrote:
> On 2012.05.06 04:43, Xiaofan Chen wrote:
>> Also now that libusbx fork is public, so I think it is not
>> a problem to expose the original fork mailing list.
>
> Except we are going to be busy enough with reinstating HID, adding
> topology, set
On 2012.05.06 03:39, Xiaofan Chen 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 IDs for OpenBSD/NetBSD for the time being,
>> and just return -1 there
On 2012.05.06 04:43, Xiaofan Chen wrote:
> Also now that libusbx fork is public, so I think it is not
> a problem to expose the original fork mailing list.
Except we are going to be busy enough with reinstating HID, adding
topology, setting up gerrit and other stuff, which are all aimed to be
co
On 6 May 2012 00:52, Peter Stuge wrote:
> Please clarify in the commit message what was changed since my
> commit, and please mention the commit id in libusb.git.
This is done in the subject. Thread ID was added. There's no need for more.
As to the libusb commit ID: Given that libusb as libusbx a
On Sun, May 6, 2012 at 11:55 AM, Xiaofan Chen wrote:
>
> This is what I have under OpenBSD and I think it looks fine.
>
Similar for NetBSD (6.0 Beta).
bash-4.2$ ./listdevs
[timestamp] [threadID] facility level [function call]
-
14 matches
Mail list logo
