git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [kernel.org users] Re: auto-packing on kernel.org? please?
Date: Sun, 16 Oct 2005 11:44:46 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0510161122570.23242@iabervon.org> (raw)
In-Reply-To: <435264B1.2010204@de.bosch.com>

On Sun, 16 Oct 2005, Dirk Behme wrote:

> > On Thu, 13 Oct 2005, Jeff Garzik wrote:
> >
> > >I have real users of my git repos who can't just download a 100MB pack file
> > >in
> > >an hour, it takes them many hours.
> 
> Seems that I'm one of these users (but using an other repo).
> 
> Pack files are very nice saving bandwith and disk space. But what I dislike is
> that I often have to download same information twice: Remote .git/objects/*
> repo grows and I update my local repo daily against this. Then once a
> month/release/whatever .git/objects/* are packed into one file. This new pack
> file then is downloaded as well, but most/all of the information in this file
> is already in my local repo and downloaded again. Something like
> 
> - detect that there is new pack file in remote repo
> - check what is in this remote pack file
> - if in local repo no or only few .git/objects/* are missing, download the
> missing ones and create an identical copy of remote pack file using local
> .git/objects/*. Don't download remote pack file.

This is the problem: it's impossible to download only a few objects from a 
pack file from an HTTP server, because those don't exist on the server as 
separate files.

The current HTTP code actually never downloads a pack file unless a needed 
object is not anywhere else, at which point it has no choice but to 
download the pack.

	-Daniel
*This .sig left intentionally blank*

  reply	other threads:[~2005-10-16 15:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 18:44 auto-packing on kernel.org? please? Linus Torvalds
     [not found] ` <434EABFD.5070604@zytor.com>
     [not found]   ` <434EC07C.30505@pobox.com>
2005-10-13 21:23     ` [kernel.org users] " Linus Torvalds
2005-10-16 14:33       ` Dirk Behme
2005-10-16 15:44         ` Daniel Barkalow [this message]
2005-10-16 16:12           ` Nick Hengeveld
2005-10-16 16:23             ` Brian Gerst
2005-10-16 16:56               ` Junio C Hamano
2005-10-16 21:33                 ` Nick Hengeveld
2005-10-16 22:12                   ` Junio C Hamano
2005-10-17  6:06                     ` Nick Hengeveld
2005-10-17  8:21                       ` Junio C Hamano
2005-10-17 17:41                         ` Nick Hengeveld
2005-10-17 20:08                           ` Junio C Hamano
2005-10-17 22:56                             ` Daniel Barkalow
2005-10-17 23:19                               ` Linus Torvalds
2005-10-17 23:54                             ` Nick Hengeveld
2005-10-17 19:13                   ` Daniel Barkalow
2005-10-16 17:10               ` Johannes Schindelin
2005-10-16 17:15               ` Brian Gerst
2005-11-21 19:01 ` Carl Baldwin
2005-11-21 19:24   ` Linus Torvalds
2005-11-21 19:58     ` Junio C Hamano
2005-11-21 20:38       ` Linus Torvalds
2005-11-21 21:35         ` Junio C Hamano
2005-11-22  5:26     ` Chuck Lever
2005-11-22  5:41       ` Linus Torvalds
2005-11-22 14:13         ` Catalin Marinas
2005-11-22 17:05           ` Linus Torvalds
     [not found]           ` <7v64qkfwhe.fsf@assigned-by-dhcp.cox.net>
     [not found]             ` <b0943d9e0511220946o3b62842ey@mail.gmail.com>
     [not found]               ` <7v1x18eddp.fsf@assigned-by-dhcp.cox.net>
2005-11-23 14:10                 ` Catalin Marinas
2005-11-22 18:18         ` Chuck Lever
2005-11-23 14:18           ` Catalin Marinas
2005-11-22 17:25     ` Carl Baldwin
2005-11-22 17:58       ` Linus Torvalds

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.63.0510161122570.23242@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=dirk.behme@de.bosch.com \
    --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).