Re: [ANNOUNCE] TopGit v0.3
- From
- Jan Nieuwenhuizen <janneke-list@xs4all.nl>
- Date
- Sep 29, 2008, 10:53 UTC
- Message-ID
- <1222685623.9905.171.camel@heerbeest>
- In-Reply-To
- <20080923132728.GV10360@machine.or.cz>
On di, 2008-09-23 at 15:27 +0200, Petr Baudis wrote:
Show 6 quoted lines
> 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).
This already would be very nice and would probably remove the last technical hurdle to switch. Is it also easy to detect if a branch is a leaf node?
Show 5 quoted lines
> 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...
Ah, so the problem is about branches depending on a branch from which a dependency is removed. What is it that we need to be looking for by history walking? Can't we possibly keep/cache that info in a special topgit file?
Jan.
-- Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org