Re: [Libusb-devel] Stuff to do before next release

[Michael P. <mic...@gm...>]

Peter Stuge wrote:
>> Michael Plante wrote:
>> > >> SW-toggleable logging was never planned for this release
>> >
>> > Neither were several of the other things on the list, and unlike
>> > most of those, the logging patches are already basically done.
>>
>> Those logging patches should also be pretty easy to rebase, right?


I seem to recall there were potential conflicting problems independently
introduced later on into libusb.git (possibly relating to usbi_dbg not
working in certain cases), but I'm not certain.  In any case, the
logging-during-first-half-of-libusb_init problem wasn't really resolved, as
far as I know.  Pete could probably answer these more easily, but it sounds
like he believes these could wait.  I suppose I can wait, too, then.  I was
primarily annoyed that the patches had been reverted in libusb-pbatard.git,
just to try to bring it into sync with libusb.git.  This would have been a
decent place for a topic branch, but, either way, I still have them in my
repo (which I haven't had a chance to look at, much less rebase, lately).




Pete Batard wrote:
>> libusb.git lacks the MSVC project files, which makes it inconvenient to
>> create branches from it, as I'm doing 90% of libusb development using
>> MSVC. I can work around it, but it's a hell of a lot more convenient to
>> do development off my branch, and, once I'm pleased with that
>> development, retrofit for libusb.git.

Yes, this is a headache.  I hope it can be resolved soon (by including the
msvc files in the official repo).  The temporary solution is to have twice
as many branches, and, for each pair, have one branch with all the MSVC
commits up front, and another with the commits in the order we expect them
to be applied in.  Fun...

Michael