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 do not see why "git commit" should automatically update version.h in the first place. Users should use a _released_ source tarball or binary installer so major, minor, micro is enough. Developers should use git and know what version they use. In a RERO world normal users should not use a git version. I have no objection to provide intermediary/test versions with a mano version. But that can be managed locally by the developer providing the intermediary version. No need to store the nano version in git. 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
