From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Giorgos Keramidas Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Mon, 7 Jan 2008 10:33:32 +0200 Message-ID: <20080107083332.GA2490@kobe.laptop> References: <20080103010807.GB13318@kobe.laptop> <85wsqqnfce.fsf@lola.goethe.zz> <85bq80mgut.fsf@lola.goethe.zz> <85fxxbjjk2.fsf@lola.goethe.zz> <85odbydpat.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199694844 3572 80.91.229.12 (7 Jan 2008 08:34:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Jan 2008 08:34:04 +0000 (UTC) Cc: esr@snark.thyrsus.com, rms@gnu.org, emacs-devel@gnu.org, esr@thyrsus.com, acm@muc.de, eliz@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 07 09:34:23 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JBnR8-0005Qp-Qg for ged-emacs-devel@m.gmane.org; Mon, 07 Jan 2008 09:34:23 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBnQl-0006bg-U6 for ged-emacs-devel@m.gmane.org; Mon, 07 Jan 2008 03:33:59 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBnQh-0006aO-Ic for emacs-devel@gnu.org; Mon, 07 Jan 2008 03:33:55 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBnQg-0006YR-D6 for emacs-devel@gnu.org; Mon, 07 Jan 2008 03:33:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBnQg-0006YG-97 for emacs-devel@gnu.org; Mon, 07 Jan 2008 03:33:54 -0500 Original-Received: from mx-out.forthnet.gr ([193.92.150.104] helo=mx-out-01.forthnet.gr) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBnQV-0007A2-Nx; Mon, 07 Jan 2008 03:33:44 -0500 Original-Received: from mx-av-02.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-01.forthnet.gr (8.13.8/8.13.8) with ESMTP id m078XeYs021644; Mon, 7 Jan 2008 10:33:40 +0200 Original-Received: from MX-IN-02.forthnet.gr (mx-in-02.forthnet.gr [193.92.150.185]) by mx-av-02.forthnet.gr (8.14.1/8.14.1) with ESMTP id m078XeA4009699; Mon, 7 Jan 2008 10:33:40 +0200 Original-Received: from kobe.laptop (ppp5-162.adsl.forthnet.gr [62.1.228.162]) by MX-IN-02.forthnet.gr (8.14.2/8.14.2) with ESMTP id m078XbhF022708; Mon, 7 Jan 2008 10:33:38 +0200 Authentication-Results: MX-IN-02.forthnet.gr smtp.mail=keramida@ceid.upatras.gr; spf=neutral Authentication-Results: MX-IN-02.forthnet.gr header.from=keramida@ceid.upatras.gr; sender-id=neutral Original-Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m078Xbwj002544; Mon, 7 Jan 2008 10:33:37 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Original-Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m078XWq8002543; Mon, 7 Jan 2008 10:33:32 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Content-Disposition: inline In-Reply-To: <85odbydpat.fsf@lola.goethe.zz> X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:86446 Archived-At: On 2008-01-07 09:15, David Kastrup wrote: >Richard Stallman writes: >> "the current development version" is not a concept for git. No >> repository is special as far as git is concerned. The "current >> development version" is a social, not a technical concept. For example, >> the git maintainer was off-line unexpectedly for some months recently. >> Somebody else took over seamlessly by collecting, arranging and >> coordinating patches on the git list into _his_ repository. >> >> With CVS, people can get the current version of every program on >> savannah in a uniform way. What you say seems to imply that that is >> not possible with git. That seems like a big step backwards. > > Huh? Declare a repository as official, and people can sync to it and > "get the current version of every program on Savannah in a uniform way". > They can sync to any other repository (or pull changes on top of other > already pulled changes), too, without disturbing their setup. But it is > not like they would magically get something they didn't ask for, or > would not always be able to tell what changes in addition to the > Savannah remote state they had applied in their own repository. I think there's a misunderstanding, but it's ok. Richard, the main `new feature' of a DVCS is not that it changes anything about the `central' repository. It would still be possible to name a well defined, well known place where the official Emacs source tree lives. Since savannah is a well known place for Emacs, that's where the official tree should be, of course. >> Within a community of people that work together, it won't be a >> problem. They will know to look THERE instead of HERE. But users in >> general can't be expected to check for that sort of thing before they >> get the current development Emacs. > > Huh? I can get an rsync of Emacs CVS, check something into that copy > and publish it on a server. Same thing. A user can't usefully work > with two CVS repositories at once, sure, but the THERE/HERE confusion is > just the same. ... and this scratches the surface of the `new feature' of a DVCS. There is still a `central' repository, which is well known and used for the official releases. But developers can *also* collaborate with each other by directly exchanging changesets with each other. They don't have to specificlly go through a single CVS tree to do this. They still *can* go through the `central' repository for all their work, it's just not mandatory. - Giorgos