From: "Matthias Andree" <matthias.andree@gmx.de>
To: thomas@koch.ro, "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "John Tapsell" <johnflux@gmail.com>, git@vger.kernel.org
Subject: Re: encrypted repositories? with git-torrent?
Date: Mon, 20 Jul 2009 14:13:31 +0200 [thread overview]
Message-ID: <op.uxc78tdp1e62zd@balu.cs.uni-paderborn.de> (raw)
In-Reply-To: <200907182109.31275.thomas@koch.ro>
Am 18.07.2009, 21:09 Uhr, schrieb Thomas Koch <thomas@koch.ro>:
> Wouldn't this be a use case for git-torrent?
> http://code.google.com/p/gittorrent/
> http://repo.or.cz/w/VCS-Git-Torrent.git
>
> As I understand it, all data would be stored decentraliced and the
> (optional?) central server only saves, who has which objects.
I wonder about latency and accessibility here if clients are disconnected.
Seems this is more for transferring repositories to large numbers of
customers as sort of content distribution network for high load, rather
than low connectivity - and the latter is my prime concern and also a
detail of my scenario.
--
Matthias Andree
next prev parent reply other threads:[~2009-07-20 12:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 15:14 encrypted repositories? Matthias Andree
2009-07-17 16:06 ` Michael J Gruber
2009-07-17 20:22 ` Jakub Narebski
2009-07-17 16:30 ` Matthias Kestenholz
2009-07-17 19:38 ` Linus Torvalds
2009-07-17 20:22 ` John Tapsell
2009-07-17 20:40 ` Linus Torvalds
2009-07-17 20:42 ` Linus Torvalds
2009-07-18 19:09 ` encrypted repositories? with git-torrent? Thomas Koch
2009-07-20 12:13 ` Matthias Andree [this message]
2009-07-20 12:09 ` encrypted repositories? Matthias Andree
2009-07-20 13:48 ` Jakub Narebski
2009-07-21 8:30 ` Matthias Andree
2009-07-20 15:30 ` Jeff King
2009-07-21 8:25 ` Matthias Andree
2009-07-23 10:40 ` Jeff King
2012-08-02 14:52 ` J-S-B
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=op.uxc78tdp1e62zd@balu.cs.uni-paderborn.de \
--to=matthias.andree@gmx.de \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--cc=thomas@koch.ro \
--cc=torvalds@linux-foundation.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).