Pete Batard wrote: > Also, if say you're using TortoiseGit on Windows to fetch the repo, > and compile in a MinGW environment where git is not available (since > git isn't installed by default there), you will fail to populate the > last field.
Yes. As you all know I like to optimize for the common case (not doing debugging) even at the cost of adding complexity or requirements for more uncommon cases (doing debugging) so the somewhat wacky development environment you describe is easy to prioritize down. Experience shows that it is often not really critical to identify the commit, usually the micro version is enough. But here and there the commit will make it into the code, and then that's a nice bonus. I'm curious to see how often it will actually show up in debug logs. I have no idea what to expect! :) > The limitations above are the precise reason we went for a nano in > libusbx... It's an interesting setup! //Peter ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
