From: Ted Ts'o <tytso@mit.edu>
To: Luke Kenneth Casson Leighton <luke.leighton@gmail.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: git pack/unpack over bittorrent - works!
Date: Sat, 4 Sep 2010 18:41:39 -0400 [thread overview]
Message-ID: <20100904224139.GD4887@thunk.org> (raw)
In-Reply-To: <AANLkTikAfSrfKRaK3ozXV_eT6Rd-VRbXQUQLk3SY8QnJ@mail.gmail.com>
On Sat, Sep 04, 2010 at 09:00:56PM +0100, Luke Kenneth Casson Leighton wrote:
> > Which brings me back to my original question --- what problem exactly
> > are you trying to solve? What's the scenario?
>
> i described those in prior messages. to summarise: they're basically
> reduction of dependence on centralised infrastructure, and to allow
> developers to carry on doing code-sprints using bugtrackers, wikis and
> anything else that can be "git-able" as its back-end, _even_ in the
> cases where there is little or absolutely no bandwidth... and _still_
> sync up globally once any one of the developers gets back online.
So at all of the code sprints I've been at, the developers all have
locally very good bandwidth between each other. And if they don't
have wifi, what *will* they have? In the example you gave, you never
were able to bring up a local area network, because you had one or two
lamers who couldn't even do wifi in adhoc mode. Hell, even if you had
to hook up someone's laptop using an RS-232 line and PPP, that would
be plenty of bandwidth for git. So you weren't specific enough in
your scenario. How could it happen? And is it really all that realistic?
Even if it did, it wouldn't be hard to just set up a git server on one
of the laptop. What makes peer2peer so critically important in this
use case? (And no, carrier pigeons are not particularly realistic for
a code sprint....)
- Ted
next prev parent reply other threads:[~2010-09-04 22:42 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 14:36 git pack/unpack over bittorrent - works! Luke Kenneth Casson Leighton
2010-09-01 22:04 ` Nguyen Thai Ngoc Duy
2010-09-02 13:37 ` Luke Kenneth Casson Leighton
2010-09-02 13:53 ` Luke Kenneth Casson Leighton
2010-09-02 14:08 ` Ævar Arnfjörð Bjarmason
2010-09-02 15:33 ` A Large Angry SCM
2010-09-02 15:42 ` Luke Kenneth Casson Leighton
2010-09-02 15:51 ` Luke Kenneth Casson Leighton
2010-09-02 17:06 ` A Large Angry SCM
2010-09-02 15:58 ` Jeff King
2010-09-02 16:41 ` Nicolas Pitre
2010-09-02 17:09 ` A Large Angry SCM
2010-09-02 17:31 ` Nicolas Pitre
2010-09-02 19:17 ` Luke Kenneth Casson Leighton
2010-09-02 19:29 ` Shawn O. Pearce
2010-09-02 19:51 ` Luke Kenneth Casson Leighton
2010-09-02 20:06 ` Luke Kenneth Casson Leighton
2010-09-03 0:36 ` Nicolas Pitre
2010-09-03 10:34 ` Luke Kenneth Casson Leighton
2010-09-03 17:03 ` Junio C Hamano
2010-09-02 20:28 ` Brandon Casey
2010-09-02 20:48 ` Luke Kenneth Casson Leighton
2010-09-02 20:45 ` Jakub Narebski
2010-09-02 21:10 ` Luke Kenneth Casson Leighton
2010-09-02 21:19 ` Luke Kenneth Casson Leighton
2010-09-03 0:29 ` Nicolas Pitre
2010-09-03 2:48 ` Nguyen Thai Ngoc Duy
2010-09-03 10:55 ` Luke Kenneth Casson Leighton
2010-09-03 10:23 ` Luke Kenneth Casson Leighton
2010-09-03 10:54 ` Luke Kenneth Casson Leighton
2010-09-02 18:07 ` Luke Kenneth Casson Leighton
2010-09-02 18:23 ` Casey Dahlin
2010-09-02 16:58 ` A Large Angry SCM
2010-09-02 17:21 ` Nicolas Pitre
2010-09-02 19:41 ` Luke Kenneth Casson Leighton
2010-09-02 19:52 ` A Large Angry SCM
2010-09-02 23:09 ` Nicolas Pitre
2010-09-03 10:37 ` Theodore Tso
2010-09-03 11:04 ` Luke Kenneth Casson Leighton
2010-09-03 17:12 ` Junio C Hamano
2010-09-03 18:31 ` Ted Ts'o
2010-09-03 19:41 ` Nicolas Pitre
2010-09-03 21:11 ` Luke Kenneth Casson Leighton
2010-09-04 0:24 ` Nguyen Thai Ngoc Duy
2010-09-04 0:57 ` Nguyen Thai Ngoc Duy
2010-09-04 1:52 ` Artur Skawina
2010-09-04 4:39 ` Nicolas Pitre
2010-09-04 5:42 ` Artur Skawina
2010-09-04 6:13 ` Nicolas Pitre
2010-09-04 11:58 ` Luke Kenneth Casson Leighton
2010-09-04 13:14 ` Luke Kenneth Casson Leighton
2010-09-05 2:16 ` Nicolas Pitre
2010-09-05 18:05 ` Luke Kenneth Casson Leighton
2010-09-05 23:52 ` Nicolas Pitre
2010-09-06 13:23 ` Luke Kenneth Casson Leighton
2010-09-06 16:51 ` Nicolas Pitre
2010-09-06 22:33 ` Luke Kenneth Casson Leighton
2010-09-06 23:34 ` Junio C Hamano
2010-09-06 23:57 ` Nicolas Pitre
2010-09-07 0:17 ` Luke Kenneth Casson Leighton
2010-09-07 0:29 ` Luke Kenneth Casson Leighton
2010-09-04 13:42 ` Artur Skawina
[not found] ` <20100904155638.GA17606@pcpool00.mathematik.uni-freiburg.de>
2010-09-04 17:23 ` Artur Skawina
2010-09-04 18:46 ` Artur Skawina
2010-09-04 1:57 ` Theodore Tso
2010-09-04 5:23 ` Kyle Moffett
2010-09-04 11:46 ` Theodore Tso
2010-09-04 14:06 ` Luke Kenneth Casson Leighton
2010-09-05 1:32 ` Nicolas Pitre
2010-09-05 17:16 ` Luke Kenneth Casson Leighton
2010-09-04 5:40 ` Nicolas Pitre
2010-09-04 12:00 ` Theodore Tso
2010-09-04 12:44 ` Luke Kenneth Casson Leighton
2010-09-04 14:50 ` Luke Kenneth Casson Leighton
2010-09-04 18:14 ` Ted Ts'o
2010-09-04 20:00 ` Luke Kenneth Casson Leighton
2010-09-04 22:41 ` Ted Ts'o [this message]
2010-09-05 17:22 ` Luke Kenneth Casson Leighton
2010-09-04 20:20 ` Jakub Narebski
2010-09-04 20:47 ` Luke Kenneth Casson Leighton
2010-09-04 21:16 ` Jakub Narebski
2010-09-04 21:24 ` Luke Kenneth Casson Leighton
2010-09-04 22:47 ` Ted Ts'o
2010-09-05 1:43 ` Tomas Carnecky
2010-09-05 1:18 ` Nicolas Pitre
2010-09-05 17:25 ` Luke Kenneth Casson Leighton
2010-09-06 0:05 ` Nicolas Pitre
2010-09-04 12:33 ` Luke Kenneth Casson Leighton
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=20100904224139.GD4887@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke.leighton@gmail.com \
--cc=nico@fluxnic.net \
/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).