Jakub Narebski <jnareb@xxxxxxxxx> writes: > This concludes easiest part of autodetecting compile configuration > using autoconf generated configure script. Patches needs revision by > somebody better versed in autoconf than me. Thanks. Will take a look. > About needing autoconf to build git: > > 1. Currently using autoconf is totally optional, so one can compile > git as one used to earlier. This should stay this way, at least for now and probably even after merging this into "master" someday (we need to get this in "next" first). > 2. configure script generated by autoconf can be treated exactly the > same like html and man documentation generated by asciidoc: use > separate 'configure' branch to store current version of configure > script, and add autogeneration of configure script to the same hook > like generating html and man documentation. Actually my gut feeling on this is eventually (read: when the autoconfiguration is stable enough) we would want to do this the other way around --- keep only the generated configure script for public consumption, and interested parties can check out autoconf branch to hack on configure.ac and friends when needed. But we haven't reached that point yet, so we will see. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html