>
> Right. And the interesting things about looking at the relationship
> between "whole project tree" merges and their relationship to business
> rules and project managment is that:
>
> 1) Whole project tree merging is a good fit for reasonable business
> rules/project mgt. People don't talk about "the GCC patch to
> files so and so" -- they talk about "the [implicitly: whole tree]
> patch to GCC that adds feature X or fixes bug Y".
Say what?
This is a bad example.
People talk about patches to files so and so all the time in GCC.
Unless you are changing something about the actual intermediate
represenation in GCC (IE reducing the size of the tree structures by
moving members around, etc), or adding macros to *all* targets (or all
configs of a target), generally, you don't touch more than maybe a few
files.
That would be madness in terms of trying to find bugs if most patches
didn't touch < 5 files.
Pick a different example.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 13 07:21:10 2003