git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: David Lang <david.lang@digitalinsight.com>
Cc: git@vger.kernel.org
Subject: Re: Last mile to 1.0?
Date: Sun, 17 Jul 2005 22:44:08 -0700	[thread overview]
Message-ID: <7vackkekif.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0507161815100.15383@qynat.qvtvafvgr.pbz> (David Lang's message of "Sat, 16 Jul 2005 18:18:24 -0700 (PDT)")

David Lang <david.lang@digitalinsight.com> writes:

> a very common one will be prople who want to setup a cron job to
> update their local tree nightly, in this case having a pre-generated
> pack file with each day's updates will save a significant amount of
> processing power.
>
> would it make sense to have it do something along the lines of sending
> the day;s pack file plus a small number of individual object (even if
> the pack file will partially duplicate object the puller already has)

I think that would be a reasonable thing to do.  The server for
anonymous puller, git-daemon, may need some extending.  As
people criticised, git-upload-pack/git-fetch-pack protocol being
not easily extensible, we would end up doing another protocol,
though, that's OK.

Fortunately [*1*], git-daemon itself is written to be extensible
if you are willing to introduce a totally new protocol driver,
so if this on-demand pack generation turns out to be too much
a resource hog, we have a reasonably easy way out.


[Footnote]

*1* We are fortunate but that is not by dumb luck.  When he did
daemon.c::execute(), Linus must have thought things through.

  reply	other threads:[~2005-07-18  5:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-16 17:46 Last mile to 1.0? Junio C Hamano
2005-07-16 18:36 ` Eric W. Biederman
2005-07-17  0:49   ` Junio C Hamano
2005-07-17  1:18     ` David Lang
2005-07-18  5:44       ` Junio C Hamano [this message]
2005-07-18  4:53 ` Alexey Nezhdanov
2005-07-18  5:35   ` Junio C Hamano
2005-07-18  6:48     ` Alexey Nezhdanov
2005-07-18  7:38       ` Junio C Hamano
2005-07-23  8:15 ` Ryan Anderson
2005-07-23 12:56   ` Gene Heskett
2005-07-24  0:53   ` [PATCH 0/6] A bit better dumb server support Junio C Hamano
2005-07-23  8:50 ` Last mile to 1.0? Ryan Anderson
2005-07-23 13:14   ` Gene Heskett
2005-07-23 14:47   ` Kevin Smith
2005-07-23 17:09   ` Junio C Hamano
2005-07-24  3:12     ` Alexey Nezhdanov
2005-07-29 22:41 ` Petr Baudis
2005-07-30  2:11   ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2005-07-30  5:40 barkalow
2005-07-30  8:07 ` Junio C Hamano

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=7vackkekif.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=david.lang@digitalinsight.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).