On 2012.05.02 11:39, Xiaofan Chen wrote: > I agree with you here. It is better to leave this out and only > solve this problem in the hotplug branch slated for 2.0.
On that subject, how would everyone prefer the devel/2.0 branch of libusbx to be implemented: 1. As a git branch of the current libusbx.git (i.e. switch using "git checkout devel")? 2. As a separate git repo/remote, similar to the libusbx-pbatard and libusbx-test we have at [1]? I think 1 would make it more attractive for regular git users to try upcoming 2.0 and report issues, and it should make sync'ing commits between branches easier as well. On the other hand, keeping the 1.0 and 2.0 disjoint may have its advantages. Also, I am planning to label it "-devel", as once 2.0 is released, we'll probably continue using that branch for 3.0. But if you'd prefer a different label, let me know. Regards, /Pete [1] http://libusbx.git.sourceforge.net/git/gitweb-index.cgi ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
