git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <sbejar@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCHv2] clone: support cloning full bundles
Date: Mon, 25 Feb 2008 21:29:22 +0100	[thread overview]
Message-ID: <8aa486160802251229x778c7427nd51093bc23ec6c8c@mail.gmail.com> (raw)
In-Reply-To: <7vlk58j0k1.fsf@gitster.siamese.dyndns.org>

On Mon, Feb 25, 2008 at 8:30 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Santi Béjar <sbejar@gmail.com> writes:
>
>  > Signed-off-by: Santi Béjar <sbejar@gmail.com>
>  > ---
>  >
>  > Hi *,
>  >
>  >   while waiting for the C port of git-clone I've updated my patch to
>  > support bundles in "git clone".
>
>  I do not recall the v1 round of this patch, but it does not look
>  too bad.

Well, it was during the freeze, you probably had more important things to do :-)

http://article.gmane.org/gmane.comp.version-control.git/68035

>
>  I was hoping, however, if we can replace "git fetch-pack" there
>  with "git-fetch" so that you do not have to have the if
>  conditional based on "$repo"'s type.  Isn't "git fetch" capable
>  of fetching from a bundle already?
>

"git fetch" is capable to fetch bundles, but to use "git fetch"
instead of "git fetch-pack"
you need to reorganize other things (not the same output, to download
all the refs you need to write a config with refs/heads/*:..., "git
fetch" does not have a --no-progress), so I opted for
a minimal path (and not break the most used path :-).

I sent another patch to convert every transport to "git fetch" in:

http://article.gmane.org/gmane.comp.version-control.git/65669

but it had some problems (ups now I see I didn't answer to Johannes
Schindelin's reply, sorry, or I cannot find it). At the end as
git-clone was going to be ported to C...

Santi

  reply	other threads:[~2008-02-25 20:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 10:12 [PATCHv2] clone: support cloning full bundles Santi Béjar
2008-02-25 19:30 ` Junio C Hamano
2008-02-25 20:29   ` Santi Béjar [this message]
2008-02-25 21:00     ` Junio C Hamano
2008-02-27 22:44 ` Junio C Hamano
2008-02-27 23:04   ` Santi Béjar
2008-02-27 23:16     ` Santi Béjar
2008-02-27 23:48       ` Daniel Barkalow
2008-02-28  0:19       ` Junio C Hamano
2008-02-28  0:26         ` Johannes Schindelin
2008-02-28  0:32           ` Santi Béjar
2008-02-29  4:27           ` Mark Levedahl
  -- strict thread matches above, loose matches on Subject: below --
2008-02-28  2:22 [PATCHv3] " Santi Béjar
2008-02-29 19:16 ` [PATCHv2] " 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=8aa486160802251229x778c7427nd51093bc23ec6c8c@mail.gmail.com \
    --to=sbejar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).