From: Johannes Sixt <j.sixt@viscovery.net>
To: Clemens Buchacher <drizzd@aon.at>
Cc: Shawn Pearce <spearce@spearce.org>, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
netroby <hufeng1987@gmail.com>,
Git Mail List <git@vger.kernel.org>,
Tomas Carnecky <tom@dbservice.com>
Subject: Re: New Feature wanted: Is it possible to let git clone continue last break point?
Date: Fri, 04 Nov 2011 10:35:35 +0100 [thread overview]
Message-ID: <4EB3B1E7.7080507@viscovery.net> (raw)
In-Reply-To: <20111104085633.GA13924@ecki>
Am 11/4/2011 9:56, schrieb Clemens Buchacher:
> Cache ... not the pack but the information
> to re-create it...
It has been discussed. It doesn't work. Because with threaded pack
generation, the resulting pack is not deterministic.
-- Hannes
next prev parent reply other threads:[~2011-11-04 9:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEZo+gfKVY-YgMjd=bEYzRV4-460kqDik-yVcQ9Xs=DoCZOMDg@mail.gmail.com>
2011-10-31 2:28 ` New Feature wanted: Is it possible to let git clone continue last break point? netroby
2011-10-31 4:00 ` Tay Ray Chuan
2011-10-31 9:07 ` Jonathan Nieder
2011-10-31 9:16 ` netroby
2011-11-02 22:06 ` Jeff King
2011-11-02 22:41 ` Junio C Hamano
2011-11-02 23:27 ` Jeff King
2011-11-03 0:06 ` Shawn Pearce
2011-11-03 2:42 ` Jeff King
2011-11-03 4:19 ` Shawn Pearce
2011-11-04 8:56 ` Clemens Buchacher
2011-11-04 9:35 ` Johannes Sixt [this message]
2011-11-04 14:22 ` Shawn Pearce
2011-11-04 15:55 ` Jakub Narebski
2011-11-04 16:05 ` Nguyen Thai Ngoc Duy
2011-11-05 10:00 ` Clemens Buchacher
2011-10-31 9:14 ` Jakub Narebski
2011-10-31 12:49 ` Michael Schubert
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=4EB3B1E7.7080507@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hufeng1987@gmail.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=tom@dbservice.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.