On Fri, Apr 23, 2010 at 6:06 AM, Jakob Bornecrantz <ja...@vmware.com> wrote: > On 2010-04-23 13.03, Keith Whitwell wrote: >> >> On Fri, 2010-04-23 at 04:12 -0700, Jakob Bornecrantz wrote: >> >>> >>> Hi all >>> >>> So mesa has a fair bit of branches just laying around not doing >>> anything. I wrote a quick script that prints the branch name and the >>> number of commits that this branch has which are not on the master >>> branch. I have attached a full list but here is a random short list: >>> >>> gallium-s3tc: 0 >>> gallium-sampler-view: 0 >>> gallium-screen-context: 3 >>> gallium-softpipe-winsys: 1 >>> gallium-st-api: 0 >>> gallium-st-api-dri: 0 >>> gallium-strict-aliasing: 0 >>> gallium-sw-api: 6 >>> gallium-sw-api-2: 0 >>> gallium-targets: 0 >>> gallium-tex-surfaces: 0 >>> gallium-texture-transfer: 0 >>> gallium-tgsi-semantic-cleanup: 0 >>> gallium-util-format-is-supported: 1 >>> gallium-vertex-linear: 0 >>> gallium-vertexelementcso: 0 >>> gallium-wgl-rework: 0 >>> gallium-winsys-handle: 7 >>> gallium-winsys-handle-rebased: 0 >>> gallium-winsys-private: 1 >>> >>> Quite a fair bit branch that has no special commits, is it okay to >>> remove those? I know this a bit of throwing a stone in a glass house >>> considering I'm responsible for a fair bit, 4 of those just from the >>> list in the mail. >>> >> >> I've been removing dead branches for quite a while now as I find them& >> have motivation. Certainly I think we can remove all the "zero"s... >> > > Right, hmm it looks like git doesn't remove local remote branches > automatically, so my list is quite outdated. Here is a updated list, have > removed one zero branch that was mine. And I'm probably am going to remove > gallium-winsys-handle (which got rebased).
FYI, "git remote prune", "git pull --prune" and "git fetch --prune" can handle this for you. -- Dan _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
