[RFC] Enforcing a "linear" repository by first parent?

[Mark A. Flacy]

On Thu, 2009-03-19 at 15:26 -0400, Greg Ward wrote:

[snip]
> Less smart-alecky response: embrace the brave new world.  Branches and
> merges happen all the time, so why not let your history reflect that?
> Use rebase if you don't want so many silly little merge changesets.
> 
> Disclaimer: it sounds nice on paper, but I haven't fully embraced the
> brave new world myself yet.  I mean, yeah, sure, I've used hg and git
> to prepare and submit patches to a couple of projects, and I use hg
> for my own piddling little spare-time projects, but we haven't taken
> the plunge at work.  Yet.  ;-)


We deal with a ClearCase/UCM version of the "brave new world" at work
every day.  Sure, the version tree graph of any given file can be rather
imposing, but you can still designate a "main branch" and deliver
everything into that one.

A path down a single branch is a linear one.

-- 
Mark A. Flacy <mflacy at verizon.net>