From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 22 May 2014 09:03:23 -0400
To: 9fans@9fans.net
Message-ID: <2f1ad3bcc87faee08cf6eb9e19ce7f89@mikro.quanstro.net>
In-Reply-To: <20140522051121.690A5B82A@mail.bitblocks.com>
References: <9bef3191d2c415d1031b0d3dc02aebfb@proxima.alt.za>
	<ef104fcf2d033121a8bbb49117deb623@ladd.quanstro.net>
	<CAJSxfmLuk=m0iGBFuEJA7vG9JqgpdSspzwQndMZCCba5F3MohQ@mail.gmail.com>
	<20140522001334.DC674B82A@mail.bitblocks.com>
	<96D6CED6-EF41-4D65-8E96-DBA9D6724718@corpus-callosum.com>
	<20140522051121.690A5B82A@mail.bitblocks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] CMS/MMS (VCS/SCM/DSCM) [was: syscall 53]
Topicbox-Message-UUID: ed16d306-ead8-11e9-9d60-3106f5b1d025

> Branch/merge features evolved in response to people's needs.
> Merging is necessary if you (as an organization) have
> substantial local changes for your product (or internal
> use) and you also want to use the latest release from your
> vendor. No amount of namespace manipulation is going to
> help you. Parallel development is inherently more headachy!

i have not found this to be a problem when maintaining
9atom.  simply evaluate patches as they come in.

- erik