From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Stephens Subject: Re: Hello All and Seeking Information Date: Mon, 24 Nov 2008 16:35:16 +0000 Message-ID: <804p1xgjzv.fsf@tiny.isode.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org To: "Tim Visher" X-From: git-owner@vger.kernel.org Mon Nov 24 17:36:42 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1L4eQP-0006pc-V0 for gcvg-git-2@gmane.org; Mon, 24 Nov 2008 17:36:38 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753214AbYKXQfW (ORCPT ); Mon, 24 Nov 2008 11:35:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753075AbYKXQfW (ORCPT ); Mon, 24 Nov 2008 11:35:22 -0500 Received: from rufus.isode.com ([62.3.217.251]:42529 "EHLO rufus.isode.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751083AbYKXQfV (ORCPT ); Mon, 24 Nov 2008 11:35:21 -0500 Received: from tiny.isode.net (shiny.isode.com [62.3.217.250]) by rufus.isode.com (smtp internal) via TCP with SMTP id ; Mon, 24 Nov 2008 16:35:18 +0000 Received: by tiny.isode.net (sSMTP sendmail emulation); Mon, 24 Nov 2008 16:35:18 +0000 X-Hashcash: 1:20:081124:tim.visher@gmail.com::VsJsPUs9w5MRQ12N:0000000000000000000000000000000000000000001Td X-Hashcash: 1:20:081124:git@vger.kernel.org::KU7/6mP0M6b4h5+X:0000000000000000000000000000000000000000002gzM In-Reply-To: (Tim Visher's message of "Mon\, 24 Nov 2008 11\:28\:22 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: "Tim Visher" writes: [...] > However, there are some issues that I can't wrap my head around, > such as how you can guarantee that all developers are working on the > same code-base without a central repo. You can't. That's the point. If developers wish to use a central repository and always to work based on that, then they can. But the tool doesn't enforce that. describes a common (IME) benefit. [...]