Cody Permann <codyperm...@gmail.com> writes: > Well, yes... I used that tip from Roy to see all the pull requests. > There around 80 of them out there already in the short life of libMesh > on github. 95% of those have long been merged back into trunk but > that ref spec still shows them all. It's not a big deal, I have an > alias for 'git branch -av' but I'll probably just drop the '-a'. > Problem solved!
It may not solve the problem because showing remote branches is useful. Personally, I just use 'git ls-remote' to see the remotes and git pull origin pull/123/head to attempt merging. If I want to passively look at what's there, I might: git fetch origin pull/123/head git show FETCH_HEAD I don't know if github has a way to expire or hide those heads better so that prune can do its thing. FWIW, we use named topic branches in PETSc and occasionally batch-prune topic branches that have been merged to 'master' for a while. So when I accept a pull request, I always bring it into a named branch. That is partly an artifact of integrating in 'next' before merging to 'master', but it's easier to keep track of when you have descriptive branch names. ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
