git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: git@vger.kernel.org
Subject: Re: I: git-fetch: -n option disappeared but git-fetch(1) still describe it
Date: Wed, 12 Mar 2008 15:52:23 +0100	[thread overview]
Message-ID: <47D7EE27.50407@op5.se> (raw)
In-Reply-To: <20080312105102.GE14040@wo.int.altlinux.org>

Dmitry V. Levin wrote:
> Hi,
> 
> git-fetch builtinification (commit v1.5.3.2-93-gb888d61) apparently
> dropped -n option (alias to --no-tags) documented in
> Documentation/fetch-options.txt
> 
> Either builtin-fetch.c or Documentation/fetch-options.txt should be
> adjusted to sync the code with its docs.
> 
> Original bug report:
> https://bugzilla.altlinux.org/show_bug.cgi?id=14870
> 

I have a (very) vague memory that git-fetch.sh had to iterate over
tags one by one, making tag-heavy projects excruciatingly slow to
fetch from with the shellscript version. Some pathological case
with 2700 tags was presented where a fetch took nearly an hour,
iirc. AFAIR, the builtinification (or was it a protocol extension?)
reduced that time to something around 10 seconds for the pathological
case.

Does anyone else have a sharper memory of what caused the -n option
to be dropped?

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2008-03-12 14:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 10:51 I: git-fetch: -n option disappeared but git-fetch(1) still describe it Dmitry V. Levin
2008-03-12 14:52 ` Andreas Ericsson [this message]
2008-03-12 16:04   ` Johannes Schindelin
2008-03-12 16:06     ` Andreas Ericsson
2008-03-12 16:11       ` Johannes Schindelin
2008-03-13  6:50         ` Andreas Ericsson
2008-03-13  7:13           ` [PATCH] git fetch: Take '-n' to mean '--no-tags' Andreas Ericsson
2008-03-13  7:30             ` Junio C Hamano

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=47D7EE27.50407@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=ldv@altlinux.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).