From: John Tapsell <johnflux@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Automatically remote prune
Date: Thu, 5 Nov 2009 10:41:26 +0900 [thread overview]
Message-ID: <43d8ce650911041741w4b39d137ha2a1529a15256d27@mail.gmail.com> (raw)
In-Reply-To: <7v639qi2un.fsf@alter.siamese.dyndns.org>
2009/11/5 Junio C Hamano <gitster@pobox.com>:
> John Tapsell <johnflux@gmail.com> 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.
John
next prev parent reply other threads:[~2009-11-05 1:41 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 [this message]
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=43d8ce650911041741w4b39d137ha2a1529a15256d27@mail.gmail.com \
--to=johnflux@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).