All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: "git mailing list" <git@vger.kernel.org>
Subject: Re: [RFC] repack vs re-clone
Date: Mon, 11 Feb 2008 20:51:26 +0100	[thread overview]
Message-ID: <200802112051.27271.jnareb@gmail.com> (raw)
In-Reply-To: <e5bfff550802111120x24338cd6n6eb1f6db55fe487f@mail.gmail.com>

Marco Costalba wrote:
> On Feb 11, 2008 7:45 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> > "Marco Costalba" <mcostalba@gmail.com> writes:
> >
> > > So it happens to be just faster to re-clone the whole thing by upstream.
> >
> > So what you are doing is passing the work, unnecessary work I'd say,
> > to some poor server. Not nice.
> 
> To a poor net bandwidth I would say because cloning from zero just
> downloads the packages.

Cloning from zero over http, https and rsync (and ftp) just downloads
the packfiles. Cloning over git or ssh if I understand correctly[*1*]
generates single pack for transfer. And that generates load for server.

[*1*] If I undersnad correctly from discussions here on git mailing
      list, the pack transfer protocol currently can transfer only
      _single_ pack; proposed multi-pack extension didn't get
      implemented.
-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2008-02-11 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10  8:25 [RFC] repack vs re-clone Marco Costalba
2008-02-10 20:50 ` Nicolas Pitre
2008-02-11 18:45 ` Jakub Narebski
2008-02-11 19:20   ` Marco Costalba
2008-02-11 19:50     ` Johannes Schindelin
2008-02-11 19:51     ` Jakub Narebski [this message]
2008-02-11 20:44       ` Nicolas Pitre
2008-02-11 19:40   ` Nicolas Pitre
2008-02-11 19:53     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200802112051.27271.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@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 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.