On Thu, Sep 11, 2008 at 10:03:12AM +0200, Jan Nieuwenhuizen wrote: > The last implementation would just recreate a branch with all new > dependencies, which is quite inefficient when you're just removing > or adding one (and the list of dependencies is long, say ~100). But this is rewriting history, isn't it? This would make your work completely different from others' and that violates one of main TopGit's design goals. Or am I missing something obvious? Currently, I'm thinking that something like .topundeps (or !-prefixing dependencies in .topdeps) is the only way to implement this... -- Petr "Pasky" Baudis The next generation of interesting software will be done on the Macintosh, not the IBM PC. -- Bill Gates -- 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
