On 3/6/07, Bill Lear <rael@xxxxxxxxxx> wrote:
No, I think you missed my point. There are two xyz.o's: One in .master/xyz.o, and one in .branchX/xyz.o. So, you're example becomes:
For most users, there are no dedicated branch-specific build directories. In any situation where there _are_ such branch/arch/config-option specific builddirs, someone has crafted a neat multi-<factor> build system. Now, if you have such a build system, it's trivial to have a separate checkout for each branch. Trying to push this bit of complexity into git means that git would have an option that lets most users shoot themselves in the foot, big time. So - your ideas are OK, but just do all the trickery and magic for the super-build-system _in_ the super-build-system. You don't need any GIT changes, just take advantage of the really fast and lightweight "local clone". I guess that's the definition of "WRONG" above. It's wrong and error-prone for most users, and for the handsome few that could take advantage of it, there are better ways of doing it. cheers, martin - To unsubscribe from this list: 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