From: Luke Kenneth Casson Leighton <luke.leighton@gmail.com>
To: cdahlin@redhat.com
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] Introduce git-hive
Date: Mon, 30 Aug 2010 22:17:07 +0100 [thread overview]
Message-ID: <AANLkTikcV6f=bUBa-F44JCEFOT0dHrvgrLY-j9hvvOyX@mail.gmail.com> (raw)
In-Reply-To: <1283198367-11440-1-git-send-email-cdahlin@redhat.com>
On Mon, Aug 30, 2010 at 8:59 PM, <cdahlin@redhat.com> wrote:
> From: Casey Dahlin <cdahlin@redhat.com>
>
> This isn't really what I'd normally call ready for public consumption, but
> since there's been some minimal list chatter on a similar subject I figured I'd
> put this out there early.
>
> git-hive is a peer to peer service for exchanging branches. When started it
> runs a small daemon to publish your repository on a random (or specified) port.
> Two hive daemons connected to oneanother can exchange branch lists and
> introduce eachother to more hive daemons to widen the network.
p.s. is there any location where, in diagrammatic form, the
protocol's described?
next prev parent reply other threads:[~2010-08-30 21:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 19:59 [RFC PATCH] Introduce git-hive cdahlin
2010-08-30 21:17 ` Luke Kenneth Casson Leighton [this message]
2010-08-31 1:29 ` Nguyen Thai Ngoc Duy
2010-08-31 14:38 ` Casey Dahlin
2010-08-31 15:08 ` Luke Kenneth Casson Leighton
2010-08-31 15:52 ` Casey Dahlin
2010-08-31 16:47 ` Luke Kenneth Casson Leighton
2010-08-31 17:20 ` Casey Dahlin
[not found] ` <815C806E-E7DC-4B7D-9B45-4C9B289DFEEF@sb.org>
2010-08-31 19:19 ` Casey Dahlin
2010-08-31 19:21 ` Kevin Ballard
2010-08-31 19:25 ` Casey Dahlin
2010-09-05 20:08 ` Tomas Carnecky
2010-09-06 2:28 ` Casey Dahlin
2010-08-31 19:23 ` Kevin Ballard
2010-09-01 3:56 ` Ilari Liusvaara
2010-09-01 4:07 ` Casey Dahlin
2010-09-05 19:48 ` Giuseppe Bilotta
[not found] ` <20100905194810.5940F384096@mbox.dmi.unict.it>
2010-09-06 2:25 ` Casey Dahlin
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='AANLkTikcV6f=bUBa-F44JCEFOT0dHrvgrLY-j9hvvOyX@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).