From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dhruva Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Mon, 7 Jan 2008 10:06:16 +0530 Message-ID: References: <20080101171120.GC3830@muc.de> <20080103010807.GB13318@kobe.laptop> <85wsqqnfce.fsf@lola.goethe.zz> <85bq80mgut.fsf@lola.goethe.zz> <85fxxbjjk2.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1199680593 4046 80.91.229.12 (7 Jan 2008 04:36:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Jan 2008 04:36:33 +0000 (UTC) Cc: esr@snark.thyrsus.com, emacs-devel@gnu.org, esr@thyrsus.com, keramida@ceid.upatras.gr, acm@muc.de, eliz@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 07 05:36:53 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 1JBjjG-0002KL-FL for ged-emacs-devel@m.gmane.org; Mon, 07 Jan 2008 05:36:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBjit-0002Jg-6P for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 23:36:27 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBjip-0002J2-88 for emacs-devel@gnu.org; Sun, 06 Jan 2008 23:36:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBjil-0002Dd-N0 for emacs-devel@gnu.org; Sun, 06 Jan 2008 23:36:22 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBjil-0002DO-Jf for emacs-devel@gnu.org; Sun, 06 Jan 2008 23:36:19 -0500 Original-Received: from wa-out-1112.google.com ([209.85.146.176]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBjil-0003Rb-3E for emacs-devel@gnu.org; Sun, 06 Jan 2008 23:36:19 -0500 Original-Received: by wa-out-1112.google.com with SMTP id k34so12312236wah.10 for ; Sun, 06 Jan 2008 20:36:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=lD7PyF7eyRY3CMD1Tl56VcFTT/J1SeVaH9tii7oMBfM=; b=ntmGbkuyNwCJzxQUbRsPibHhYN1lKSDi83OcW+VbmDFheMTVYoaDpW16UlDspjSvwZS76jEorqWtr6l77sP7EOzzWCIPpQm6WoZnIn5RirRsGlJucKigjTb7xwfL1KXgpz580nb/e4/ZANuiKnLLTM/ckr4EBcc6qFqRAPVFZdY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JG7qoOrnxPAAh3Al16FRyQJLzGGm1bMwROosxJco1V6KauSCDtD9QZb/b/7VgIlk/kVWodPaxtsRqjc7l/Miqa0mCa1LooDxtQAnqXHIrDdK05pdwumIc3KMCRhj087aoEaz9y2K41rU6/UE3h5x3ZSHqwpL+DoW3EfeCX3Tszo= Original-Received: by 10.115.47.1 with SMTP id z1mr8832238waj.117.1199680577096; Sun, 06 Jan 2008 20:36:17 -0800 (PST) Original-Received: by 10.115.73.12 with HTTP; Sun, 6 Jan 2008 20:36:16 -0800 (PST) In-Reply-To: Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:86427 Archived-At: Hello, On Jan 7, 2008 9:48 AM, Richard Stallman wrote: > 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. There can still be one _offcial_ repository from which "people" (non core developer community) can pull from. This could be equivalent to the current HEAD. The only difference would be that in CVS, every core developer checks into the _official_ repository where as in a dVCS, the maintainer can pull in the changes from the various core developers (or core developers can push) into it. > 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. The above work flow would allow a single point access to the latest as it is in the current state with CVS. You could treat all other dVCS repositories belonging to various developers and different features as current branches in CVS. As the users know of HEAD in CVS, IMO, they will easily (I presume) learn about "master" in GIT or "default" in mercurial. with best regards, dhruva -- Contents reflect my personal views only!