git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git peer-to-peer project: info needed

From
CDCasey Dahlin <cdahlin@redhat.com>
Date
Aug 30, 2010, 17:45 UTC
Message-ID
<20100830174506.GB9955@fearengine.rdu.redhat.com>
In-Reply-To
<20100830173905.GA9955@fearengine.rdu.redhat.com>
On Mon, Aug 30, 2010 at 01:39:07PM -0400, Casey Dahlin wrote:
Show 20 quoted lines
> On Sun, Aug 29, 2010 at 10:56:27PM +0100, Luke Kenneth Casson Leighton wrote:
> > hi folks,
> > 
> > [please could you kindly cc on responses because i am subscribed with
> > "no mail" set]
> > 
> > i need some guidance on what i should be doing, to add peer-to-peer
> > networking to "git fetch".  i can take care of the peer-to-peer
> > networking side: the bit i'm unsure about is what sequence of events
> > are required to happen.  i'm presently looking at the use of
> > walker_fetch in builtin-http-fetch.c which gives me some idea.
> > however as i aim to implement this first in python not c, i need to be
> > using git via command-line only.
> > 
> 
> I have a peer-to-peer git patchset that I'm already working on, which is
> nearly in a showable state. I've wanted to sand off a few more edges
> before a public review but I'll happily share it.
> 
> --CJD

On further review you seem to be talking more about making fetch itself peer-to-peer, where my patchset is more of a peer-to-peer branch-sharing mechanism. Complementary but not necessarily conflicting. Still I'll hurry up and get it online :)

--CJD
Previous: Casey DahlinNext: Luke Kenneth Casson Leighton
Message 7 of 8 in “git peer-to-peer project: info needed”
  1. Luke Kenneth Casson LeightonAug 29, 2010
  2. Jonathan NiederAug 29, 2010
  3. Luke Kenneth Casson LeightonAug 29, 2010
  4. Matthieu MoyAug 30, 2010
  5. Luke Kenneth Casson LeightonAug 30, 2010
  6. Casey DahlinAug 30, 2010
  7. Casey DahlinAug 30, 2010
  8. Luke Kenneth Casson LeightonAug 30, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.