On Wednesday 19 December 2007 10:28:32 am 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. 

Well, no, like I said, there is one and it's the only one that makes sense. A 
branch that exists is by definition not dead. And as I mentioned 
unfortunately we had to import from a system that can't handle branches so we 
have that legacy cruft.

> I don't call that easy. It takes a lot of time, especially with >50
> branches. 

To do what? Randomly pick one? Well, duh :) If you don't know what you're 
looking for the more you have the longer it will take to find.

> 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.

That procedure is called "git branch -d branchname" =) 
For now I suggest just using :
git-for-each-ref --sort=committerdate
which will give you what you want. The branches with the newest commits will 
be at the bottom. If you care then it should take at most a few minutes to 
write a script on top of that will will put "-" on ones that didn't have a 
commit in the last X hours/days/months.

z

-------------------------------------------------------------------------
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

Reply via email to