git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] clone: support cloning full bundles
Date: Wed, 12 Dec 2007 14:50:15 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0712121449310.27959@racer.site> (raw)
In-Reply-To: <1197456485-22909-1-git-send-email-sbejar@gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 265 bytes --]

Hi,

On Wed, 12 Dec 2007, Santi Béjar wrote:

> It still fails for incremental bundles.

Of course it does.  The whole point of incremental bundles is that they do 
_not_ contain all objects, but rely on some objects being present on the 
"fetch" side.

Hth,
Dscho

  reply	other threads:[~2007-12-12 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 10:48 [PATCH] clone: support cloning full bundles Santi Béjar
2007-12-12 14:50 ` Johannes Schindelin [this message]
2007-12-12 15:21   ` Santi Béjar
2007-12-12 18:46     ` Johannes Schindelin
2007-12-13  9:37       ` Santi Béjar

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=Pine.LNX.4.64.0712121449310.27959@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=sbejar@gmail.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 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).