On 12/10/09 donnoman said:

> Our team creates topic branches, then when they are ready rebases them
> and merges them into our testing branch and then deletes the old topic
> branch.
> Apparently git pull and fetch don't automatically trim the list of
> branches that it thinks origin has.
> On my local checkout a branch -a shows 20 or so branches that have
> since been deleted, but I can't get them to go away.
> Is there any facility to force it to go out and verify it's list
> against the real origin, instead of deleting the whole checkout and
> recloning?

git branch -d -r name

You're talking about remote tracking branches?

Also, one should not rebase a branch that has been made publically available.

Michael P. Soulier <msoul...@digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein

Attachment: pgp6uRH0BLKNT.pgp
Description: PGP signature

Reply via email to