git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org, dev@tools.openoffice.org,
	Jan Holesovsky <kendy@suse.cz>
Subject: Re: Git benchmarks at OpenOffice.org wiki
Date: Mon, 07 May 2007 01:05:05 -0700	[thread overview]
Message-ID: <7vk5vl6oum.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <alpine.LFD.0.98.0705042049330.3819@woody.linux-foundation.org> (Linus Torvalds's message of "Fri, 4 May 2007 20:56:08 -0700 (PDT)")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> A trivial patch is to just do
>
> 	git pack-refs --all --prune
>
> in the "git-clone.sh" script rather than force people to do it themselves, 
> but we really probably shouldn't have ever even unpacked them in the first 
> place. That is kind of stupid, but especially since that thing is written 
> in shell, it's hard to do anything smarter.

It is not just being in shell.

Although I do agree that the initial clone is special, I would
rather make clone just a thin wrapper to fetch that also happens
to perform necessary initial setup.

Keeping fetched and updated refs in core and write a packed refs
out in one go in git-fetch--tool (and later, git-fetch all in C)
would be much simpler if we do not have to worry about existing
refs (aka "git clone" special case); I am not sure if packing
refs is desirable in general for incremental "git-fetch".

  reply	other threads:[~2007-05-07  8:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 21:46 Git benchmarks at OpenOffice.org wiki Jakub Narebski
2007-05-01 22:27 ` Junio C Hamano
2007-05-02  8:55 ` Andy Parkins
2007-05-02  9:51   ` Julian Phillips
2007-05-02 10:58     ` Andy Parkins
2007-05-02 14:28       ` Julian Phillips
2007-05-02 15:30         ` Andy Parkins
2007-05-02 17:11           ` Julian Phillips
2007-05-02 14:37       ` Jan Holesovsky
2007-05-02 15:33         ` Andy Parkins
2007-05-02 17:26       ` Junio C Hamano
2007-05-02 10:24 ` Johannes Schindelin
2007-05-02 11:33   ` Jakub Narebski
2007-05-02 14:55     ` Johannes Schindelin
2007-05-05  3:56     ` Linus Torvalds
2007-05-07  8:05       ` Junio C Hamano [this message]
2007-05-07 15:22         ` Linus Torvalds
2007-05-02 14:41   ` Jan Holesovsky
2007-05-02 16:24     ` Johannes Schindelin
2007-05-02 14:24 ` Jan Holesovsky
2007-05-02 14:35   ` Johannes Schindelin
2007-05-02 16:15   ` Petr Baudis
2007-05-02 16:27     ` Jan Holesovsky
2007-05-02 16:37       ` Petr Baudis
2007-05-02 16:48         ` Petr Baudis
2007-05-02 23:30   ` Jakub Narebski
2007-05-03 11:51     ` [tools-dev] " Jan Holesovsky
2007-05-03 12:54       ` Alex Riesen
2007-05-03 15:14       ` Johannes Sixt
2007-05-04  0:48       ` Jakub Narebski
2007-05-03  7:03 ` Florian Weimer
2007-05-03  9:33   ` Johannes Schindelin
2007-05-03 10:16     ` Robin Rosenberg
2007-05-03 10:48       ` Martin Langhoff
2007-05-06 20:05         ` Robin Rosenberg
2007-05-03 23:36       ` Jakub Narebski

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=7vk5vl6oum.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dev@tools.openoffice.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=kendy@suse.cz \
    --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).