From: Sitaram Chamarty <sitaramc@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: John Tapsell <johnflux@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Automatically remote prune
Date: Thu, 5 Nov 2009 08:45:41 +0530 [thread overview]
Message-ID: <2e24e5b90911041915o40922167ob48a8503ee262b37@mail.gmail.com> (raw)
In-Reply-To: <7viqdpemki.fsf@alter.siamese.dyndns.org>
On Thu, Nov 5, 2009 at 7:53 AM, Junio C Hamano <gitster@pobox.com> wrote:
> (1) The user wants to keep the remotes/<origin>/* namespace clean (iow,
[snip]
> (2) The user does want to be careful not to lose commits that now only
This whole discussion is a conflict between those two. The current
system does the latter, safer, thing. John's users are getting
confused because they *think* this means the remote still has those
refs.
At best an alias that does a prune before (or after) a fetch should do.
And I notice 'git gui' has an option to "prune during fetch" -- maybe
that should be an option that is also made available to the CLI fetch.
next prev parent reply other threads:[~2009-11-05 3:15 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
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 [this message]
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=2e24e5b90911041915o40922167ob48a8503ee262b37@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).