git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: takis@lumumba.uhasselt.be (Panagiotis Issaris)
To: git@vger.kernel.org
Subject: Re: Problem cloning packed-and-pruned http repository
Date: Sat, 7 Oct 2006 00:05:42 +0200	[thread overview]
Message-ID: <20061006220542.GA5890@lumumba.uhasselt.be> (raw)
In-Reply-To: <20061006212616.GA5175@lumumba.uhasselt.be>

Hi

On Fri, Oct 06, 2006 at 11:26:16PM +0200 or thereabouts,  wrote:
> [...]
> I've been having trouble setting up a public repository using GIT. After
> I have pushed my repository to a directory within ~/public_html, I can
> clone it. But the repository is _big_ (261M).
> 
> So, I use "git-repack" on it and a "git-prune-packed". This makes it
> nicely fit in 14MiB. If I try to clone this pruned/packed repository
> again both cg-clone hangs on it (as does git-clone).
> [...] 
> takis@poseidon:/tmp$ cg-clone http://lumumba.uhasselt.be/takis/git/ffmpeg-h264-test.git
> defaulting to local storage area
> Fetching head...
> Fetching objects...
> Getting alternates list for http://lumumba.uhasselt.be/takis/git/ffmpeg-h264-test.git/
> Getting pack list for http://lumumba.uhasselt.be/takis/git/ffmpeg-h264-test.git/
> progress: 0 objects, 0 bytes
> cg-clone: interrupted
> 
Apparently, it does work :-/ After a _long_ time I noticed that the
repository indeed got cloned... I am not sure if this is normal behavior
or not, it seemed to take a _really_ long. I would have thought
downloading 14MiB should not take a long time on my ADSL line.


With friendly regards,
Takis

-- 
OpenPGP key: http://lumumba.uhasselt.be/takis/takis_public_key.txt
fingerprint: 6571 13A3 33D9 3726 F728  AA98 F643 B12E ECF3 E029

  reply	other threads:[~2006-10-06 22:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 21:26 Problem cloning packed-and-pruned http repository Panagiotis Issaris
2006-10-06 22:05 ` Panagiotis Issaris [this message]
     [not found]   ` <20061006194930.cf400ec4.seanlkml@sympatico.ca>
2006-10-06 23:49     ` Sean
     [not found]       ` <20061006220401.a4485d67.seanlkml@sympatico.ca>
2006-10-07  2:04         ` [RFC PATCH] Add WEBDAV timeout to http-fetch Sean
2006-10-07 10:15           ` Junio C Hamano
2006-10-07 11:27             ` Jakub Narebski
2006-10-07 17:32               ` Johannes Schindelin
2006-10-07 17:45                 ` Petr Baudis
2006-10-07 22:30                 ` Petr Baudis
2006-10-07 22:36                   ` Johannes Schindelin
2006-10-08  4:52                     ` Junio C Hamano
2006-10-08 12:03                       ` Johannes Schindelin
     [not found]                       ` <20061008091932.4d8e62d9.seanlkml@sympatico.ca>
2006-10-08 13:19                         ` Sean
2006-10-08 19:56                           ` Junio C Hamano
2006-10-11 12:13                             ` Panagiotis Issaris
2006-10-11 14:00                               ` Johannes Schindelin
2006-10-07 19:35             ` Panagiotis Issaris
2006-10-07 22:24               ` Junio C Hamano
2006-10-07  8:30         ` Panagiotis Issaris

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=20061006220542.GA5890@lumumba.uhasselt.be \
    --to=takis@lumumba.uhasselt.be \
    --cc=git@vger.kernel.org \
    /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).