All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Smart fetch via HTTP?
Date: Fri, 18 May 2007 01:14:49 +0200	[thread overview]
Message-ID: <f2inc6$hl5$1@sea.gmane.org> (raw)
In-Reply-To: 46a038f90705170709j7eb23d4fy6811fc2985dd888d@mail.gmail.com

Martin Langhoff wrote:

> On 5/18/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>> If you have a solution for that problem, please enlighten me: I don't.
> 
> Ok - worst case scenario - have a minimal hints file that tells me the
> ranges to fetch all commits and all trees. To reduce that Add to the
> hints file data to name the hashes (or even better - offsets) for the
> delta chains that contain commits+trees relevant to all the heads -
> minus 10, 20, 30, 40 commits and 1,2,4,8 and 16 days.
> 
> So there's a good chance the client can get the commits+trees needed
> efficiently. For blobs, all you need is the index to mark the delta
> chains you need.

By the way, I think we always should get the whole delta chain, unless we
are absolutely sure that we have base object(s) in repo.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2007-05-17 23:10 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 20:10 Smart fetch via HTTP? Jan Hudec
2007-05-15 22:30 ` A Large Angry SCM
2007-05-15 23:29 ` Shawn O. Pearce
2007-05-16  0:38   ` Junio C Hamano
2007-05-16  5:25 ` Martin Langhoff
2007-05-16 11:33   ` Johannes Schindelin
2007-05-16 21:26     ` Martin Langhoff
2007-05-16 21:54       ` Jakub Narebski
2007-05-17  0:52       ` Johannes Schindelin
2007-05-17  1:03         ` Shawn O. Pearce
2007-05-17  1:04           ` david
2007-05-17  1:26             ` Shawn O. Pearce
2007-05-17  1:45               ` Shawn O. Pearce
2007-05-17 12:36                 ` Theodore Tso
2007-05-17  3:45           ` Nicolas Pitre
2007-05-17 10:48             ` Johannes Schindelin
2007-05-17 14:41               ` Nicolas Pitre
2007-05-17 15:24                 ` Martin Langhoff
2007-05-17 15:34                   ` Nicolas Pitre
2007-05-17 20:04                 ` Jan Hudec
2007-05-17 20:31                   ` Nicolas Pitre
2007-05-17 21:00                     ` david
2007-05-18  9:01                   ` Johannes Schindelin
2007-05-18 17:51                     ` Jan Hudec
2007-05-17 11:28         ` Matthieu Moy
2007-05-17 13:10           ` Martin Langhoff
2007-05-17 13:47             ` Johannes Schindelin
2007-05-17 14:05               ` Matthieu Moy
2007-05-17 14:09               ` Martin Langhoff
2007-05-17 15:01                 ` Nicolas Pitre
2007-05-17 23:14                 ` Jakub Narebski [this message]
2007-05-17 14:50               ` Nicolas Pitre
2007-05-17 12:40 ` Petr Baudis
2007-05-17 12:48   ` Matthieu Moy
2007-05-18 18:27     ` Linus Torvalds
2007-05-18 18:33       ` alan
2007-05-18 19:01       ` Joel Becker
2007-05-18 20:06         ` Matthieu Moy
2007-05-18 20:13         ` Linus Torvalds
2007-05-18 21:56           ` Joel Becker
2007-05-20 10:30             ` Jan Hudec
2007-05-19  0:50       ` david
2007-05-19  3:58         ` Shawn O. Pearce
2007-05-19  4:58           ` david
2007-05-17 20:26   ` Jan Hudec
2007-05-17 20:38     ` Nicolas Pitre
2007-05-18 17:35       ` Jan Hudec

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='f2inc6$hl5$1@sea.gmane.org' \
    --to=jnareb@gmail.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 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.