From: Junio C Hamano <gitster@pobox.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Automatically remote prune
Date: Wed, 04 Nov 2009 10:04:00 -0800 [thread overview]
Message-ID: <7v639qi2un.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 43d8ce650911040242l44bbf87dm35494e04ce9039aa@mail.gmail.com
John Tapsell <johnflux@gmail.com> writes:
> $> git branch -r
> origin/blah1 [Deleted]
> origin/blah2
>
> (Some branches have been deleted on the remote server. Use "git
> remote prune origin" to remove these)
There is no information locally available to do this, unless you are
willing to contact the remote every time somebody says "branch -r" (or
"branch -a"). I tend to think it is not very nice for the branch command
that has long been a "local" command to suddenly start talking to outside
world.
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.a
The [Deleted] mark in your suggestion tells the user:
This is already removed in the remote, and this tracking copy is the
only way for you to view it ever again. Do not run 'remote prune
origin' blindly otherwise you will lose it.
But that is already possible with "git remote show origin", isn't it?
next prev parent reply other threads:[~2009-11-04 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 10:42 Automatically remote prune John Tapsell
2009-11-04 18:04 ` Junio C Hamano [this message]
2009-11-05 1:41 ` John Tapsell
2009-11-05 2:00 ` Shawn O. Pearce
2009-11-05 2:23 ` Junio C Hamano
2009-11-05 3:15 ` Sitaram Chamarty
2009-11-05 8:05 ` John Tapsell
2009-11-05 20:05 ` Junio C Hamano
2009-11-05 23:09 ` Jay Soffian
2009-11-06 0:17 ` Petr Baudis
2009-11-06 0:38 ` Jay Soffian
2009-11-06 10:31 ` Petr Baudis
2009-11-08 19:08 ` Junio C Hamano
2009-11-06 0:16 ` Petr Baudis
2009-11-05 13:19 ` Dmitry Potapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v639qi2un.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).