Sent from my evil iPad On Apr 8, 2013, at 8:14 PM, Jed Brown <jedbr...@mcs.anl.gov> wrote:
> Cody Permann <codyperm...@gmail.com> writes: > >> Ah close - looks like I need 'git pull --prune'! > > I guess I don't know what you're looking for. You want to prune the > remote tracking branch while it still exists upstream? That's not > really the point of remote tracking branches so you should just make > sure they are closed upstream. 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! > > Note that you can always: > > $ git pull origin pull/123/head > > which will not create a new remote tracking branch when you perform the > pull. ------------------------------------------------------------------------------ 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
