git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <luke.leighton@gmail.com>
To: Casey Dahlin <cdahlin@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: git peer-to-peer project: info needed
Date: Mon, 30 Aug 2010 22:22:03 +0100	[thread overview]
Message-ID: <AANLkTinjow-aRmNB7rSgq17ww00csN82tWBM+6Nv350k@mail.gmail.com> (raw)
In-Reply-To: <20100830174506.GB9955@fearengine.rdu.redhat.com>

On Mon, Aug 30, 2010 at 6:45 PM, Casey Dahlin <cdahlin@redhat.com> wrote:

> On further review you seem to be talking more about making fetch itself
> peer-to-peer,

 only on the basis that that's what i believed would be a good start,
lacking any experience or advice :)

> where my patchset is more of a peer-to-peer branch-sharing
> mechanism.

 what's the difference?  i did look at making "blobs / trees"
available but i figured that that would just get you a snapshot (not
helpful).  i'm afraid i don't actually know the difference between
fetch sharing and branch sharing, as my knowledge of git internals is
a bit "swiss cheese".


> Complementary but not necessarily conflicting. Still I'll
> hurry up and get it online :)

 commented already.  was a bit of a bit message in the inbox, with an
inline thingy rather than attachment, but i'll cope.

l.

      reply	other threads:[~2010-08-30 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29 21:56 git peer-to-peer project: info needed Luke Kenneth Casson Leighton
2010-08-29 22:06 ` Jonathan Nieder
2010-08-29 22:57   ` Luke Kenneth Casson Leighton
2010-08-30  6:56 ` Matthieu Moy
2010-08-30 11:31   ` Luke Kenneth Casson Leighton
2010-08-30 17:39 ` Casey Dahlin
2010-08-30 17:45   ` Casey Dahlin
2010-08-30 21:22     ` Luke Kenneth Casson Leighton [this message]

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=AANLkTinjow-aRmNB7rSgq17ww00csN82tWBM+6Nv350k@mail.gmail.com \
    --to=luke.leighton@gmail.com \
    --cc=cdahlin@redhat.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).