From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric S. Raymond" Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Fri, 4 Jan 2008 07:45:47 -0500 Organization: Eric Conspiracy Secret Labs Message-ID: <20080104124545.GD16402@thyrsus.com> 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> Reply-To: esr@thyrsus.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199450832 32673 80.91.229.12 (4 Jan 2008 12:47:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 4 Jan 2008 12:47:12 +0000 (UTC) Cc: acm@muc.de, eliz@gnu.org, emacs-devel@gnu.org, esr@snark.thyrsus.com To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 04 13:47:30 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 1JAlxK-0004pH-M7 for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2008 13:47:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JAlwt-0002Em-Nt for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2008 07:46:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JAlwq-0002EY-Hu for emacs-devel@gnu.org; Fri, 04 Jan 2008 07:46:52 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JAlwp-0002EI-4n for emacs-devel@gnu.org; Fri, 04 Jan 2008 07:46:52 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JAlwp-0002EF-0H for emacs-devel@gnu.org; Fri, 04 Jan 2008 07:46:51 -0500 Original-Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=snark.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JAlvq-0000UY-95; Fri, 04 Jan 2008 07:45:52 -0500 Original-Received: by snark.thyrsus.com (Postfix, from userid 23) id EE45F830697; Fri, 4 Jan 2008 07:45:49 -0500 (EST) Content-Disposition: inline In-Reply-To: X-Eric-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.15+20070412 (2007-04-11) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:86059 Archived-At: Richard Stallman : > Does this mean there is no concept of "trunk"? When someone who is > not normally a participant in the project decides to "download the > current sources", which revision does he get? More precisely, what > determines which revision he gets? 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. If you clone the repo, you get the entire history -- the entire DAG of revisions. Technically speaking, there is no "trunk", no distinguished branch that VCS operations treat specially. If you do an update without specifying a release or branch name, you simply get the latest sequential revision. Socially, the "trunk" is probably the branch the last release tarball was taken from. Some of these systems support named branches. When that's so, you can label a branch "trunk" if you like. -- Eric S. Raymond