> > I may be slow today, but I don't see how merging the metadata is going
> > to accomplish all this [stuff that vendor branches do].
Merge Metadata can serve the same function as the vendor branch.
Typical scenario, a local copy of an open source project, maybe say cvs.
Ill describe a scenario of how you could use this hypothetical cvs to
develop the features to get to the hypothetical version.
- You import the initial rev onto the main branch. (Say 1.10.8
or whatever)
- You create your own private branch (called named_trunk) to make your
changes for say the naming of the main trunk
- Lots of work happens on cvs to fix bugs etc, or to add new
subcommands like lsvtree.
- You now import a new rev onto the main branch (Say 1.10.9
or something)
- Now to update your private branch you just do a merge from the main
branch by doing something like "cvs up -j main"
- Even more work happens on cvs to fix bugs etc, or to add new
subcommands
- You now import a new rev onto the main branch (Say 1.10.10
or something)
- Now to update your private branch you just do a merge from the
main branch by doing something like "cvs up -j main". But the
difference now is that it only merges in the differences from your
last merge.
This model also allows you to have multiple private branches doing all
kinds of various things that are unrelated to each other. Perhaps
one to add rename support, another to add merge meta-data etc.
> And how did merging (meta)data get into this thread? I'm not signing
> up for _that_, no matter how many people refuse to change the
> subject line. ;-) Waaaay too hard, and I'm not really sure I even like the
> idea anyway.
> -- steve
I agree its hard, but its very useful for big software projects with
multiple parallel lines of development its essential.
If you havent done multiple parallel lines of development (ie. like 3
or more) you wont see the benefit because you havent felt the pain.
Serious tools like ClearCase have these, until cvs does it wont be
considered in the same league as ClearCase.
-----------------------------------------------------------------------
John Cavanaugh Agilent Technologies
R&D Program Manager 1400 Fountaingrove Pkwy
CAD Data Store Santa Rosa, CA 95403-1799
Email: [EMAIL PROTECTED] Phone: 707-577-4780
707-577-3948 (Fax)
-----------------------------------------------------------------------
Be happy with your progress, but always discontented
enough to continue to improve your skills.
-- Unknown
-----------------------------------------------------------------------
