[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What a modern collaboration toolkit looks like

From: Eric S. Raymond
Subject: Re: What a modern collaboration toolkit looks like
Date: Fri, 4 Jan 2008 07:45:47 -0500
User-agent: Mutt/1.5.15+20070412 (2007-04-11)

Richard Stallman <address@hidden>:
> 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.  
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]