From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] git-clone: don't unpack objects
Date: Wed, 19 Oct 2005 13:58:36 -0700 [thread overview]
Message-ID: <7virvt441v.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0510191327560.3369@g5.osdl.org> (Linus Torvalds's message of "Wed, 19 Oct 2005 13:31:53 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> No, I think the unconditional --keep is fine for clone.
>
> What to do about incremental pulls is not as clear, but I think the clone
> case is pretty much obvious these days.
>
> The main reason for unpacking was that packs used to be "strange". These
> days, packs are arguably the _common_ thing.
OK, that makes sense.
I'd move this 'unconditional keep' to clone-pack. The --keep
flag becomes a no-op.
prev parent reply other threads:[~2005-10-19 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 12:43 [PATCH] git-clone: don't unpack objects Timo Hirvonen
2005-10-19 20:09 ` Junio C Hamano
2005-10-19 20:23 ` Johannes Schindelin
2005-10-19 20:31 ` Linus Torvalds
2005-10-19 20:58 ` Junio C Hamano [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=7virvt441v.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).