Matthias Hopf wrote: > On Dec 19, 07 09:38:35 -0500, Zack Rusin wrote: >> On Wednesday 19 December 2007 09:20:06 am Matthias Hopf wrote: >>> I very much agree on that. Partially, this is a problem with git, which >>> does not show you which of the branches are already completely merged >>> into another branch (read: might be dead). >> Well, that's not how it works. Git knows exactly the merge points, but what >> you call a "dead" branch in Git is one that doesn't exist. In this >> particular > > I think I made that clear. No, there is no notion of dead branches in > gti. But yes, there *are* dead branches. Just git doesn't know about it, > but it *could* guess about it. And yes, they can always be revived. > >> As to the relevance of the branches it's easy to check by doing >> "git log origin/branchname". And in any way the thing about branches is that >> you need to know what you're looking for otherwise just making the number of >> them smaller so that people can randomly be checking them out is not helping >> the situation. > > I don't call that easy. It takes a lot of time, especially with >50 > branches. Git could easily add a (+) or so after a branch if it is > completely merged in a different branch and that has been more than - > say - two weeks ago. Or even hide it (with or without some option). > >> While I agree that the branches which are not developed anymore should be >> deleted, realistically speaking someone would have to go back and see >> whether >> the CVS import actually encoded in the history when a branch X has been >> actually *merged* into master, otherwise, as Michel pointed out, we'll be >> just losing history and that's likely not worth it. > > Losing history is never worth it, right. But maybe we can get some idea > of what is needed in git to have it better distinguish between (truly) > live and (eventually) dead branches.
Maybe old branches could be renamed with a "closed" or "dead" suffix. I don't have a strong opinion about it though. -Brian ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
