git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
	Linus <torvalds@linux-foundation.org>
Subject: A local shared clone is now much slower
Date: Mon, 8 Jul 2013 13:03:55 +1000	[thread overview]
Message-ID: <20130708130355.647fffb6e5b6a453bfa0fa6e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

Hi guys,

So commit 0433ad128c59 ("clone: run check_everything_connected") (which
turned up with v1.8.3) added a large traversal to clone which (as the
comment said) makes a clone much slower.  It is especially noticeable on
"git clone -s -l -n" which I use every day and used to be almost
instant.  Is there any thought to making it fast again, please?

The above clone is very useful for working with different branches in one
tree without touching every file in the main branch you are working
with (and consequent issues with rebuilding at least).  As linux-next
maintainer, you can imagine that I do this a bit.

I am sure one of Linus' points about branches was that being able to make
a fast local clone of a tree to use more than one branch was a feature.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-07-08  3:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  3:03 Stephen Rothwell [this message]
2013-07-08  3:20 ` A local shared clone is now much slower Duy Nguyen
2013-07-08  4:25   ` Stephen Rothwell
2013-07-08  7:30 ` Jeff King
2013-07-08  8:57   ` Duy Nguyen
2013-07-08 15:00     ` Junio C Hamano
2013-07-09  4:30       ` Jeff King
2013-07-11  9:35       ` Priming git clone with a local repo? Andreas Krey
2013-07-11 16:01         ` Junio C Hamano
2013-07-08 13:05   ` A local shared clone is now much slower 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130708130355.647fffb6e5b6a453bfa0fa6e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).