From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git fetch slow as molasses due to tag downloading
Date: Fri, 15 Dec 2006 23:27:03 +0100 [thread overview]
Message-ID: <elv7av$n0$1@sea.gmane.org> (raw)
In-Reply-To: 7vtzzwn7su.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>> IMHO this should be solved as a filter: "git-show-ref --stdin
>> --show-invalid". Thus, git does not have to traverse _every_ ref for
>> _every_ incoming tag.
>
> That sounds like a too specialized hack to me. We should first
> speed up the general "--verify $ref" case; as you corrected me
> earlier it still has a useless loop.
>
> If it is still too slow (which I suspect it could be the case,
> with fork+exec overhead), we should _also_ pursue the filter
> approach, but even then I think "filter out the valid ones" is a
> specialized hack, if you mean "show only the invalid one's
> names" by --show-invalid.
>
> It would make sense to do
>
> $ git show-ref --show-invalid v1.0.0 v2.6.18
> f665776185ad074b236c00751d666da7d1977dbe refs/tags/v1.0.0
> - refs/tags/v2.6.18
>
> (and its equivalent to take refs from --stdin) though.
Nice idea. And having '-' is probably better than using
00000000000000000000000000000000000000000 as for non-existing objects.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-12-15 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 15:40 git fetch slow as molasses due to tag downloading Han-Wen Nienhuys
2006-12-14 16:05 ` Johannes Schindelin
2006-12-15 9:58 ` Jakub Narebski
2006-12-15 21:55 ` Junio C Hamano
2006-12-15 22:27 ` Jakub Narebski [this message]
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='elv7av$n0$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).