Hi, On Tue, Sep 23, 2008 at 03:13:10PM +0200, Jan Nieuwenhuizen wrote: > On ma, 2008-09-22 at 17:27 +0200, Petr Baudis wrote: > [about adding and removing topic branch dependencies] > > > Do you really expect you will need this kind of functionality often, > > though? > > Yes. This is what people are used to and do now with our patches based > system. We cannot take away such basic functionality. Also, currently > it is very easy to do, however, it is quite error prone. That's also > why using [top]git would be so great. > > There are ~300 topic branches. Usually, a combination of most of these > is used as the master branch. There are a number of scenarios where > you would want to add/remove some of these topic branches from master. > > The most pressing case for this is for packagers making a release. > Unless we also make their life easier, we can forget about moving to > [top]git. I think that would be possible to do, too. ;-) It really depends on how general your patch tree is - what we can't make to work is just the most generic case, but e.g. if master is a *leaf* branch nothing else depends on and it can't get the branch through multiple paths, you can do the dependency removal rather easily (if it can get through multiple paths, you can still do it but you might have to deal with big conflicts). But if you scenario indeed is totally generic, I'm afraid I don't know how to make TopGit remove dependencies, except perhaps for the price of massive complexity and massive slowdown (pretty much redoing all the history walking etc.). Maybe someone else comes by with a genial solution... -- 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
