2012/5/1 Pete Batard <p...@akeo.ie>: > By the way, do you still consider the update of version.h and the > running of autotools that results as something you want to see fixed? As > I said, we can move the nano into its own nano.h to avoid the issue, but > I'm not sure of how important you or anybody else sees that issue right now.
I think that having a modification of libusb/version.h with each commit is a bad idea. I just got the problem. It is impossible to apply (using git am) a serie of patches if the LIBUSB_NANO has been modified between the patch serie generation and the patch serie applying. I think it will be also impossible to rebase a (local) branch (without manual conflicts fixes). So I have disabled the git hooks to automatically update the LIBUSB_NANO in my repositories. Bye -- Dr. Ludovic Rousseau ------------------------------------------------------------------------------ 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
