Thread (9 messages) flat view 9 messages, 6 authors, 2016-06-15

Re: Automatically remote prune

From: Shawn O. Pearce <hidden>
Date: 2016-06-15 22:47:40

John Tapsell [off-list ref] wrote:
2009/11/5 Junio C Hamano [off-list ref]:
quoted
John Tapsell [off-list ref] writes:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help