[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: What's a "trunk" good for? (apart from eating peanuts)

From: Byron Brummer <byron.brummer_at_livenation.com>
Date: 2007-01-12 19:25:20 CET

B. Smith-Mannschott wrote:
> On 1/11/07, Byron Brummer <byron.brummer@livenation.com> wrote:
>> Interesting. I'd argue that you'd hit merge points along the
>> trunk line which are at least as significant as branch points.
>> Furthermore fetching the real history could be much harder as
>> the merge likely represents much more history then was
>> included in the merge commit. [...]
>> Thus the "linear history" idea of a trunk, IMHO, really is
>> anything but. A branch-only pattern, ironically, results in
>> the ability to query for a much more linear history.
> Byron,
> Your illustration of the logical consequences of working
> 'trunkless' brought me an "aha!". I guess that's where I was
> going with my first example, but in my usual muddle I couldn't
> see it clearly.
> You're diagram illustrates that it's a good way of modeling
> software that has multiple releases and a maintenance
> lifecycle. Would you mind if I incorporated your insight into my
> presentation?

        Not at all, I'd be flattered.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 12 19:26:26 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.