From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Earl Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Sun, 06 Jan 2008 22:16:03 -0700 Message-ID: <874pdqqkq4.fsf@workhorse.earlhome> References: <20080101171120.GC3830@muc.de> <20080101.190535.32709273.wl@gnu.org> <20080101182742.GE3830@muc.de> <20080101.192802.05328072.wl@gnu.org> <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=us-ascii X-Trace: ger.gmane.org 1199682911 8682 80.91.229.12 (7 Jan 2008 05:15:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Jan 2008 05:15:11 +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 06:15:29 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 1JBkKZ-0000z6-Vt for ged-emacs-devel@m.gmane.org; Mon, 07 Jan 2008 06:15:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBkKC-0007wd-TG for ged-emacs-devel@m.gmane.org; Mon, 07 Jan 2008 00:15:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBkK8-0007vn-Qn for emacs-devel@gnu.org; Mon, 07 Jan 2008 00:14:56 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBkK6-0007ur-Lp for emacs-devel@gnu.org; Mon, 07 Jan 2008 00:14:56 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBkK6-0007uo-H4 for emacs-devel@gnu.org; Mon, 07 Jan 2008 00:14:54 -0500 Original-Received: from out02.mta.xmission.com ([166.70.13.232]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBkJv-0008NJ-Qw; Mon, 07 Jan 2008 00:14:44 -0500 Original-Received: from [166.70.13.201] (helo=mgr1.xmission.com) by out02.mta.xmission.com with esmtp (Exim 4.62) (envelope-from ) id 1JBkJr-0001Cq-Uv; Sun, 06 Jan 2008 22:14:39 -0700 Original-Received: from jearl.fttp.xmission.com ([166.70.233.10] helo=workhorse.earlhome) by mgr1.xmission.com with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1JBkJe-000827-5s; Sun, 06 Jan 2008 22:14:36 -0700 Original-Received: from jearl by workhorse.earlhome with local (Exim 4.63) (envelope-from ) id 1JBkLD-0001BI-VM; Sun, 06 Jan 2008 22:16:03 -0700 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX6+voBAQGioqL////9 /f3n5+fHx8cUFBTSngI1AAAB9UlEQVQ4jXWUwW7jIBCGUQtz9158bS3FuUayHwDJmDOyYnJFlvGe aynx63dmCOnG3aBIGL4MzPw/IJbUpvq5X0QQ3GzolY9O2JlGUoAIxrTGGBX0tG21AIcDIw0BaRjA V1FsH3DmoeQI+rThb4HtdgcU0TRd0zQqfmFEUXqHo1Z2CLSkPWCh+aJc5p89uKkpgZqXao3NoM8g vATtM8DN0x77pVQ4ElhhD+xMa5XXVPlTRP+JAe4fIEUCBqo1aAhaC/yBiCM3f+AuDovnGS/q//sx 0VLUVPJFghO+qh350bCcfWiMltpAUMdtuyXZSV0ETds1LcyX5Auq26WsZNtpNGj8TL48tEq9tp7m iz9+BwwMDMo9kHBJYNmB9xyxB/o18OzL+ntzl9Jl2bURJwInKVrrqMDyg2TX7yiKmgVXah1LQlqh dDqLiD6gfiiihtey12OMkYwif/w4RI92jeOAIqpqjWip9McqCDjr4Vg5jekqPDdl6INKh+FsMav1 bEUcqKKbmlmkK/B1KA+YFR+0cozpwPkxVY6nhCstYr4GDz/SRHHIh/oh4h1cM7jsQP0rIt6XWrY0 8WNtzipF5KwQTPyh8nXmP3IdcGT9wxsfNBuo4DWQ7PhUVE7NJ3oyJMyq4qcDRRR+cRqN6rFHPxQ/ Nljgi2fpG2hJAOwln9FOAAAAAElFTkSuQmCC In-Reply-To: (Richard Stallman's message of "Sun\, 06 Jan 2008 23\:18\:05 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (gnu/linux) Received-SPF: neutral (mgr1.xmission.com: 166.70.233.10 is neither permitted nor denied by domain of xmission.com) client-ip=166.70.233.10; envelope-from=jearl@xmission.com; helo=workhorse.earlhome; X-SA-Exim-Connect-IP: 166.70.233.10 X-SA-Exim-Mail-From: jearl@xmission.com X-Spam-DCC: XMission; sa02 1397; Body=1 Fuz1=1 Fuz2=1 X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100) X-SA-Exim-Scanned: Yes (on mgr1.xmission.com) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:86431 Archived-At: 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. A distributed VCS can be used just like CVS. The fans of distributed VCS systems like to talk about the many benefits of a distributed system, but I don't know of a single major project that uses a dVCS that doesn't have a canonical URL. For example, if you wanted to start hacking on git (assuming you had a copy of git installed already) you could do: git clone git://git.kernel.org/pub/scm/git/git.git/ If you wanted to hack on mercurial and you had a mercurial client installed you would use this command: hg clone http://selenic.com/hg/ All of the improvements to git (or mercurial) that are likely to become part of a release eventually end up in the default branch in much the same way that all of the improvements that are likely to end up in a release of emacs get put into CVS. The difference is that dVCSes like git allow for a much more flexible workflow (especially for people that spend a lot of time disconnected). > 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. Folks that like distributed version control systems (and that includes basically everyone that has tried one) like to point out that if something happened to the canonical URL work could continue on without it until things were sorted out. That doesn't mean, however, that you have to do without the canonical URL. It simply means that you *could* do without the canonical URL in a pinch. If CVS is down, you are finished until things get sorted out. With a distributed system the failure of one branch isn't more than a minor annoyance.