On 12/3/06, Linus Torvalds <torvalds@xxxxxxxx> wrote:
> If you have an old irrelevant submodule in the history that happens to > have the same name as one of them you are interested in, do you get > this as well? It could be "solved" by simply having the requirement that all modules need to be named differently (notice that "module name" is _not_ the same thing as "the directory name where the module shows up".
Okay, missed that part. I wasn't familiar with contents of the CVS modules files and misinterpreted your suggestion. MODULE [OPTIONS] [&OTHERMODULE...] [DIR] [FILES] So all this is UI only and the "normal" operations on the supermodule will just ignore what's behind the commit-links? - 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