From: Shawn O. Pearce Date: Thu, 05 Nov 2009 02:00:19 GMT Subject: Re: Automatically remote prune Message-ID: <20091105020019.GL10505@spearce.org> In-Reply-To: <43d8ce650911041741w4b39d137ha2a1529a15256d27@mail.gmail.com> John Tapsell wrote: > 2009/11/5 Junio C Hamano : > > John Tapsell writes: > > > You could store necessary information somewhere else when you contacted > > the remote the last time, but we need to consider what the benefits are to > > give this information in the first place. > > We already get all this information on a "git fetch", no? And then > promptly discard it. Surely when we do "git fetch" . So I'm talking > about just not ignoring the information we get from git fetch, but > present that information to the user. Good point. We currently don't have a provision to store this information, but we could store a list of dead remote tracking branches for reference later during `git branch -r`. Its not a lot of data, it just has little perceived value to most Git hackers because a remote branch disappears very infrequently (if ever) for most of us. -- Shawn.