From: "Marco Costalba" <mcostalba@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "git mailing list" <git@vger.kernel.org>
Subject: Re: [RFC] repack vs re-clone
Date: Mon, 11 Feb 2008 20:20:09 +0100 [thread overview]
Message-ID: <e5bfff550802111120x24338cd6n6eb1f6db55fe487f@mail.gmail.com> (raw)
In-Reply-To: <m3myq7e3ie.fsf@localhost.localdomain>
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.
next prev parent reply other threads:[~2008-02-11 19:20 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 [this message]
2008-02-11 19:50 ` Johannes Schindelin
2008-02-11 19:51 ` Jakub Narebski
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=e5bfff550802111120x24338cd6n6eb1f6db55fe487f@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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).