From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Sat, 05 Jan 2008 09:30:22 -0500 Message-ID: References: <20080101171120.GC3830@muc.de> <20080101.190535.32709273.wl@gnu.org> <20080101182742.GE3830@muc.de> <20080101.192802.05328072.wl@gnu.org> <20080102121745.GD17588@thyrsus.com> <20080104124545.GD16402@thyrsus.com> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1199543587 28724 80.91.229.12 (5 Jan 2008 14:33:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 5 Jan 2008 14:33:07 +0000 (UTC) Cc: acm@muc.de, eliz@gnu.org, emacs-devel@gnu.org, esr@snark.thyrsus.com To: esr@thyrsus.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 05 15:33:27 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 1JBA5W-0002yR-PH for ged-emacs-devel@m.gmane.org; Sat, 05 Jan 2008 15:33:27 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBA5A-0007Ac-7X for ged-emacs-devel@m.gmane.org; Sat, 05 Jan 2008 09:33:04 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBA2a-0005V0-Rd for emacs-devel@gnu.org; Sat, 05 Jan 2008 09:30:24 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBA2Z-0005US-7j for emacs-devel@gnu.org; Sat, 05 Jan 2008 09:30:24 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBA2Z-0005UM-2N for emacs-devel@gnu.org; Sat, 05 Jan 2008 09:30:23 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBA2Y-0005Jd-Sx for emacs-devel@gnu.org; Sat, 05 Jan 2008 09:30:23 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1JBA2Y-0008Nx-FX; Sat, 05 Jan 2008 09:30:22 -0500 In-reply-to: <20080104124545.GD16402@thyrsus.com> (esr@thyrsus.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:86160 Archived-At: The "current sources" is generally going to be one of the repo tip revisions packaged into a tarball by a release manager. This is not a VCS operation. That applies if/when you make a release. But what about between relesaes? Currently we recommend that people "build the source from CVS", and we don't say "from the trunk" because that is a general convention of CVS usage. If we used git, what convention would replace that? Would we have to establish our own? Would we need to maintain a file saying which branch to get and build? If so, I think the operation of adding versions to that branch would be the real analogue of a CVS commit to the urunk.